Expected behavior
Docker context desktop-linux is able to run containers without permission issues the same behavior as context default.
Actual behavior
When I run docker compose up -d certain containers enter a state of continual restarting due to permission denied issues, here is one example log message:
EXCEPTION: NSt10filesystem7__cxx1116filesystem_errorE filesystem error: cannot create directories: Permission denied
I am able to run docker commands without sudo so the permissions issue seems to only affect inside containers. When I switch the context to use docker context use default and start the containers in the same repo, the containers run with no permissions issues.
Information
- Linux distro: elementary OS
- Distro version: 6.1
- Docker Desktop Version: 4.12.0
Steps to reproduce the behavior
I am not sure if this is reproducible, this is my first time using Docker Desktop for Linux (I think it was released not too long ago). Before I ran Docker Engine and Docker Compose standalones and did not have any issues with the same codebase.
EDIT: see comment below - another user was able to reproduce
Thanks for any help on this!
Expected behavior
Docker context
desktop-linuxis able to run containers without permission issues the same behavior as contextdefault.Actual behavior
When I run
docker compose up -dcertain containers enter a state of continual restarting due to permission denied issues, here is one example log message:EXCEPTION: NSt10filesystem7__cxx1116filesystem_errorE filesystem error: cannot create directories: Permission deniedI am able to run
dockercommands withoutsudoso the permissions issue seems to only affect inside containers. When I switch the context to usedocker context use defaultand start the containers in the same repo, the containers run with no permissions issues.Information
Steps to reproduce the behavior
I am not sure if this is reproducible, this is my first time using Docker Desktop for Linux (I think it was released not too long ago). Before I ran Docker Engine and Docker Compose standalones and did not have any issues with the same codebase.
EDIT: see comment below - another user was able to reproduce
Thanks for any help on this!