You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I may be a docker newbie however, when I create a new stack, and the application compose has a separate app data directory for example /opt/appdata/applicationexample. If this directory does not exist, and I bring up the stack, it creates this directory as root. The parent directory is owned by the user the user has docker access. Is this expected?
Sorry to clarify the containers cannot write to the appdata directories (not the stacks directory) because they are running as my regular user and not root. Is this the correct behavior?
Activity
RA341 commentedon Dec 16, 2025
Yes since dockman is running as root it will create root directories.
gt9228a commentedon Dec 16, 2025
Thank you - so i should create outside of dockman or chwon after? just trying to get workflow down.
RA341 commentedon Dec 16, 2025
Up to you I mostly don't care since I no longer touch my compose folder directly
You can chown once dockman preserves perms when writing
gt9228a commentedon Dec 16, 2025
Sorry to clarify the containers cannot write to the appdata directories (not the stacks directory) because they are running as my regular user and not root. Is this the correct behavior?
RA341 commentedon Dec 16, 2025
Yes in that case you will have to chown