Docker context desktop-linux has container permission issues

[secondl1ght]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID: c66b74da-a881-4376-a708-5b140a1b5648/20220913172047

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!

[asoltys]

I ran into this issue too with containers that had mounted volumes with user permissions set to 1000:1000 which is the same uid:gid as the default user account on my host machine.

With Docker Desktop the uid:gid for the user within the container seems to have changed to 100999:100999 so updating the volume ownership permissions to that has solved the issue for me.

[ghost]

@asoltys
So does changing to 100999 help? and how do i do that...

[asoltys]

Yeah it helped me.

sudo chown -R 100999:100999 /your/volume

[ghost]

sounds like i would have to do this everytime if i set a new volume. its a solution but is not an ideal one. but thanks.

[docker-robott]

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 30 days.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

[aikaterine]

/remove-lifecycle stale

This is still an issue. Every time I set a new volume this happens,

[computerquip-work]

This makes Docker for Desktop on Linux unusable for me.

[NickSdot]

Perhaps related: #81