Closed OmarNour14 closed 1 week ago
@OmarNour14 could you please upload a diagnostic and add here your diagnostic ID? Please follow the steps here to diagnose from the terminal.
Hi @MihaelaStoica - Diagnostic ID: 54C5C807-DE17-4F26-AB65-1C356AE06AC9/20240828103828
hi, @MihaelaStoica I have the same problem Diagnostics ID: EC201E2D-7CED-447C-B9E7-3A8FB76B0D84/20240829083002 (uploaded)
Hi @MihaelaStoica - Diagnostic ID: 54C5C807-DE17-4F26-AB65-1C356AE06AC9/20240828103828
@OmarNour14, could you please also upload the diagnostic?
The command to generate + upload is:
/Applications/Docker.app/Contents/MacOS/com.docker.diagnose gather -upload
hi, @MihaelaStoica I have the same problem Diagnostics ID: EC201E2D-7CED-447C-B9E7-3A8FB76B0D84/20240829083002 (uploaded)
@andriykrasnychuk, your problem seems unrelated to the issue described here. However, some entries in your logs indicate that you have run out of space and that caused Docker Desktop to become unusable. If you have some level of access to Docker Desktop, you could try increasing the virtual disk size in Settings->Resources.
Hi @MihaelaStoica , that's the command I ran, but I can see now that the zip file didn't upload successfully. If the zip does not contain any sensitive data I am happy to upload directly to this comment.
@OmarNour14 you can run the command again and hopefully this time it will be uploaded.
@MihaelaStoica
Output:
Gathering diagnostics for ID into /var/folders/z3/_2tvbsmn70l2d6mhjqvjdjx00000gp/T/54C5C807-DE17-4F26-AB65-1C356AE06AC9/20240829134422.zip.
This may take up to 15 minutes. unable to trigger dns-forwarder diagnostics: request failed and retry attempts exhausted: Post "http://ipc/diagnostics": dial unix /Users/my-user/Library/Containers/com.docker.docker/Data/dns-forwarder.sock: connect: connection refused
Diagnostics Bundle: /var/folders/z3/_2tvbsmn70l2d6mhjqvjdjx00000gp/T/54C5C807-DE17-4F26-AB65-1C356AE06AC9/20240829134422.zip
@OmarNour14 Could you please try the following command (replacing <diagnostic ID>
with your Diagnostic ID)
/Applications/Docker.app/Contents/MacOS/com.docker.diagnose upload --id <diagnostic ID>
I'm not sure if this is the same underlying issue or not, but had Docker stop working, a "reset" worked after a couple tries, then it stopped working again. Reinstall, reset, etc. all are not working and it never starts up.
Uploaded diagnostics to: https://docker-pinata-support.s3.amazonaws.com/incoming/3/D77D6B9A-0CC1-4EB5-B5C1-D2E3B15350F0/20240829214404.zip Diagnostics ID: D77D6B9A-0CC1-4EB5-B5C1-D2E3B15350F0/20240829214404 (uploaded)
@MihaelaStoica `/Applications/Docker.app/Contents/MacOS/com.docker.diagnose upload --id 54C5C807-DE17-4F26-AB65-1C356AE06AC9/20240830064959 [2024-08-30T06:51:26.421531000Z][com.docker.diagnose.installsettings] noWindowsContainers <- true [2024-08-30T06:51:26.421868000Z][com.docker.diagnose.settingsloader] loaded settings [2024-08-30T06:51:26.423834000Z][com.docker.diagnose.public] com.docker.backend is not running so starting a local HTTP proxy SIGSEGV: segmentation violation PC=0x19b90b184 m=15 sigcode=2 addr=0x8 signal arrived during cgo execution
goroutine 88 gp=0x140006dba40 m=15 mp=0x14000700908 [syscall]: runtime.cgocall(0x1053f5bb0, 0x140005d13c8) runtime/cgocall.go:157 +0x44 fp=0x140005d1390 sp=0x140005d1350 pc=0x104866e24 github.com/docker/pinata/common/cmd/com.docker.backend/internal/systemproxy/go-ieproxy._Cfunc__getProxyUrlFromPac(0x600003d80f60, 0x600002681200) _cgo_gotypes.go:290 +0x34 fp=0x140005d13c0 sp=0x140005d1390 pc=0x104f7af54 github.com/docker/pinata/common/cmd/com.docker.backend/internal/systemproxy/go-ieproxy.getProxyForURL({0x14000160db0?, 0x32?}, {0x140005e0140, 0x32}) github.com/docker/pinata/common/cmd/com.docker.backend/internal/systemproxy/go-ieproxy/pac_darwin.go:163 +0xb0 fp=0x140005d1470 sp=0x140005d13c0 pc=0x104f7c0b0 github.com/docker/pinata/common/cmd/com.docker.backend/internal/systemproxy/go-ieproxy.(ProxyScriptConf).findProxyForURL(...) github.com/docker/pinata/common/cmd/com.docker.backend/internal/systemproxy/go-ieproxy/pac_darwin.go:146 github.com/docker/pinata/common/cmd/com.docker.backend/internal/systemproxy/go-ieproxy.(ProxyScriptConf).FindProxyForURL(...) github.com/docker/pinata/common/cmd/com.docker.backend/internal/systemproxy/go-ieproxy/ieproxy.go:53 github.com/docker/pinata/common/cmd/com.docker.backend/internal/systemproxy/go-ieproxy.(*ProxyScriptConf).FindProxyForURL-fm({0x140005e0140?, 0x7?})
@OmarNour14 In the output of the upload command, we noticed a segfault, for which we might have a fix. Would it be possible for you to try this development build and let us know if Docker Desktop starts and if not, try again to upload a dignostic? Here are the builds: Mac Apple Silicon Mac Intel
I have the same issue. I have tried the build you posted, but it doesn't work https://docker-pinata-support.s3.amazonaws.com/incoming/3/C42A4391-0070-4FBF-8A73-72AA292E9DE7/20240830111151.zip
Hi @MihaelaStoica the build you posted fixed the problem! Docker Engine up and running now for me. Thank you!
Description
I have installed Docker Desktop on my macbook using the installation guide. Upon the first Launching the Application I get the Service Agreement Page as seen below
When attempting to click on Accept I get the following error prompt:
After a few clicks the page then suddenly turns blank
When I close the tab and re-open the docker desktop app. I get a view of the Docker App console.
I can't perform any tasks on the GUI, sign-in, or change any of the settings as all the buttons are in-responsive.
The GUI after a few clicks and attempts also turns blank similar to the agreement page:
The issue appears in the following versions of docker desktop: 4.28 -> 4.33
I have tried restarting my macbook, uninstalling and re-installing the app through both homebrew cask and the official guide.
Any debugging suggestions are welcomed.
Reproduce
Expected behavior
Desktop app to work as expected
docker version
docker info
Diagnostics ID
N/A
Additional Info
No response