Skip to content

Question #138

Closed
Closed

Description

@gt9228a

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?

Activity

  1. RA341 commented on Dec 16, 2025

    @RA341
    Owner

    Yes since dockman is running as root it will create root directories.

  2. gt9228a commented on Dec 16, 2025

    @gt9228a
    Author

    Thank you - so i should create outside of dockman or chwon after? just trying to get workflow down.

  3. RA341 commented on Dec 16, 2025

    @RA341
    Owner

    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

  4. gt9228a commented on Dec 16, 2025

    @gt9228a
    Author

    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?

  5. RA341 commented on Dec 16, 2025

    @RA341
    Owner

    Yes in that case you will have to chown

  6. Repository owner locked and limited conversation to collaborators on Dec 17, 2025
  7. converted this issue into a discussion #139 on Dec 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions