-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker Desktop: Builders Application error #7356
Comments
Same issue |
Any update? |
Can you tell us if you're still reproducing with latest Docker Desktop 4.33.0? If this is still happening can you give the output of |
Hello, I still see an issue in 4.33.0. Output request:
Docker configured in System mode. Nikolai |
@nkarpysh Thanks! Looking at the output I'm not sure how files are created with Can you fix perms with:
And tell us if that fixes the issue? |
This looks very similar to #7144 (comment) |
Yeap, it did work. Now everything is fine with "Builds" section. Thx for your help. Nikolai |
Description
Application Error
We've reported this to our error tracker.
"open /Users/nkarpysh/.docker/buildx/current: permission denied"
Application Error
We've reported this to our error tracker.
"Internal Server Error"
Reproduce
Just open Docker Desktop and see it
Expected behavior
No response
docker version
Client: Docker Engine - Community Version: 27.0.3 API version: 1.45 (downgraded from 1.46) Go version: go1.22.4 Git commit: 7d4bcd863a Built: Fri Jun 28 14:56:30 2024 OS/Arch: darwin/arm64 Context: desktop-linux Server: Docker Desktop 4.31.0 (153195) Engine: Version: 26.1.4 API version: 1.45 (minimum version 1.24) Go version: go1.21.11 Git commit: de5c9cf Built: Wed Jun 5 11:29:12 2024 OS/Arch: linux/arm64 Experimental: false containerd: Version: 1.6.33 GitCommit: d2d58213f83a351ca8f528a95fbd145f5654e957 runc: Version: 1.1.12 GitCommit: v1.1.12-0-g51d5e94 docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Diagnostics ID
4009138F-141D-40CD-8229-6A573E3621E1/20240716092404
Additional Info
No response
The text was updated successfully, but these errors were encountered: