
I've got a docker swarm cluster running Appwrite with a shared file system. The appwrite service is on a separate node than the storage service and where files are storage.
When I upload a file that is a bit larger (6MB, probably needs to upload by chunk) it will fail. The logs in the appwrite service say that it got a Permission denied
when trying to rename
a file from /tmp/swoole.upfile.NliAkB
to /storage/uploads/app-.../[where the bucket files are]
.
When I try to do that myself via docker exec
using the mv
command on a file I create with touch
, I get a can't preserve ownership of '...file': Permission denied
error but the file does in-fact get moved because I can docker exec ls /storage/uploads/...
and see the file there now.
Has anyone run into this problem before?

My current theory is that Appwrite expects the permissions to be a certain way and I don't know what that way is.
Recommended threads
- Having errors migrating to cloud
Project will not migrate compeltely
- ENV vars not updating
When i do `nano .env` it shows `_APP_DOMAIN_TARGET=` as set to my domain, but when i do `docker compose exec appwrite vars` it shows `_APP_DOMAIN_TARGET=` as ...
- Index with the requested key already exi...
I'm using appwrite cli to create DB and I'm getting index_already_exists Is there a way to undestand the index name and maybe to skip if it's already exits?
