Volume issue with docker

[uniforx]

Hi .. I used this guide to start an instance of directus in docker: https://docs.directus.io/self-hosted/installation/docker.html

This is my experimental command where I mount the volumes:

docker run -d --restart=always -p 8026:8055 -v /srv/directus/:/directus --name d9 -e KEY=255d861b-5ea1-5996-9aa3-922530ec40b1 -e SECRET=6116487b-cda1-52c2-b5b5-c8022c45e263 -e ADMIN_EMAIL="[email protected]" -e ADMIN_PASSWORD="secret" directus/directus

After that I have a running directus and I can log in and creating everything. BUT in my folder /srv/directus there are only three folder created without any content. If I go inside the docker in the folder /directus/database is a sqlite database created.

What is wrong?

[br41nslug]

I think you can't mount the entire /directus folder, and if you could you shouldn't as then you can't update Directus anymore because all files would be persisted in the volume 😬

[azrikahar]

Judging from the SQLITE_CANTOPEN error, I think this is a file permission/docker mount issue and not technically an issue with Directus.

Can you try checking the container's node user UID and GID by running docker exec d9 id¹, then compare it with the host's sqlite file's user UID and GID. You will need to make sure the host's sqlite file permission matches the container's node user.

Footnotes

1. I'm using d9 as you used --name d9 in your original command, make sure to update it if it's not d9 anymore ↩

[uniforx]

This is the result ...

uid=1000(node) gid=1000(node) groups=1000(node)

[uniforx]

And you are completly right .. I set the permissions of the folder database from 755 to 777 and the database was created .. I need to mount the three volumes seperatly and set the permissions to 777 .. now it´s working.

[azrikahar]

Glad it works!

Setting 777 might be perceived as too permissive, so I think you should also be able to resolve this by using chown 1000:1000 (node user's UID and GID) for the files on the host. Similar to this solution shared by a community member: #6480 (comment)

Alternatively you might be able to extend the Directus docker image to change the node user UID and GID to match the host user as described in the docker-node docs (Directus docker image is based on this image): https://github.com/nodejs/docker-node/blob/main/docs/BestPractices.md#non-root-user, specifically this section:

If you need to change the uid/gid of the user you can use:

RUN groupmod -g 999 node && usermod -u 999 -g 999 node

[crediblebytes]

Is there a way to get this working on synology NAS? I am having the same error and passing in the user/group env vars is how I've gotten every other container to work but it doesn't seem to have an effect.
PUID: 1026
PGID: 100