Skip to content
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 GUI issue with OSX Ventura #6465

Closed
3 tasks done
jquick opened this issue Aug 31, 2022 · 25 comments
Closed
3 tasks done

Docker Desktop GUI issue with OSX Ventura #6465

jquick opened this issue Aug 31, 2022 · 25 comments

Comments

@jquick
Copy link

jquick commented Aug 31, 2022

  • I have tried with the latest version of Docker Desktop
  • I have tried disabling enabled experimental features
  • I have uploaded Diagnostics
  • Diagnostics ID: E3A0E50C-B9DE-4F85-8910-BC9AD9E20A7E/20220831133424

Expected behavior

It starts up correctly and GUI is responsive.

Actual behavior

The GUI cannot connect to the backend and is none responsive. The error from the logs seems to be (over and over):

(c0cb2e51-19) 60169025-BackendCMD C<-S NoResponse GET /ping (5.520334ms): Get "http://ipc/ping": net/http: HTTP/1.x transport connection broken: malformed HTTP response "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x<decode: missing data>

and frontend looks like:
Screenshot 2022-08-31 at 9 21 12 AM
The backend itself looks to work OK though:

❯ curl --unix-socket /var/run/docker.sock 'http://localhost/v1.41/_ping'
OK%
❯ curl --unix-socket /var/run/docker.sock 'http://localhost/v1.41/info'
{"ID":"MRI7:L37C:LFRL:V5MD:6X6B:JTHI:YE6M:FBFA:JMG6:I6D5:YPB7:PDKT","Containers":0,"ContainersRunning":0,"ContainersPaused":0,"ContainersStopped":0,"Images":0,"Driver":"overlay2","DriverStatus":[["Backing Filesystem","extfs"],["Supports d_type","true"],["Native Overlay Diff","true"],["userxattr","false"]],"Plugins":{"Volume":["local"],"Network":["bridge","host","ipvlan","macvlan","null","overlay"],"Authorization":null,"Log":["awslogs","fluentd","gcplogs","gelf","journald","json-file","local","logentries","splunk","syslog"]},"MemoryLimit":true,"SwapLimit":true,"KernelMemory":false,"KernelMemoryTCP":false,"CpuCfsPeriod":true,"CpuCfsQuota":true,"CPUShares":true,"CPUSet":true,"PidsLimit":true,"IPv4Forwarding":true,"BridgeNfIptables":true,"BridgeNfIp6tables":true,"Debug":false,"NFd":44,"OomKillDisable":false,"NGoroutines":46,"SystemTime":"2022-08-31T13:29:32.267843751Z","LoggingDriver":"json-file","CgroupDriver":"cgroupfs","CgroupVersion":"2","NEventsListener":4,"KernelVersion":"5.10.104-linuxkit","OperatingSystem":"Docker Desktop","OSVersion":"","OSType":"linux","Architecture":"aarch64","IndexServerAddress":"https://index.docker.io/v1/","RegistryConfig":{"AllowNondistributableArtifactsCIDRs":[],"AllowNondistributableArtifactsHostnames":[],"InsecureRegistryCIDRs":["127.0.0.0/8"],"IndexConfigs":{"docker.io":{"Name":"docker.io","Mirrors":[],"Secure":true,"Official":true},"hubproxy.docker.internal:5000":{"Name":"hubproxy.docker.internal:5000","Mirrors":[],"Secure":false,"Official":false}},"Mirrors":[]},"NCPU":4,"MemTotal":8232873984,"GenericResources":null,"DockerRootDir":"/var/lib/docker","HttpProxy":"http.docker.internal:3128","HttpsProxy":"http.docker.internal:3128","NoProxy":"hubproxy.docker.internal","Name":"docker-desktop","Labels":[],"ExperimentalBuild":false,"ServerVersion":"20.10.17","Runtimes":{"io.containerd.runc.v2":{"path":"runc"},"io.containerd.runtime.v1.linux":{"path":"runc"},"runc":{"path":"runc"}},"DefaultRuntime":"runc","Swarm":{"NodeID":"","NodeAddr":"","LocalNodeState":"inactive","ControlAvailable":false,"Error":"","RemoteManagers":null},"LiveRestoreEnabled":false,"Isolation":"","InitBinary":"docker-init","ContainerdCommit":{"ID":"10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1","Expected":"10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1"},"RuncCommit":{"ID":"v1.1.2-0-ga916309","Expected":"v1.1.2-0-ga916309"},"InitCommit":{"ID":"de40ad0","Expected":"de40ad0"},"SecurityOptions":["name=seccomp,profile=default","name=cgroupns"],"Warnings":null}

I am able to pull/start a container as expected.

Information

  • macOS Version: 13.0 Beta (22A5331f)
  • Intel chip or Apple chip: Apple Silicon
  • Docker Desktop Version: 2.11.1

Output of /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check

❯ /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0031: does the Docker API work?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0016: is the LinuxKit VM running?
(never continues past this point)

Steps to reproduce the behavior

  1. Install Ventura Beta6 on m1 mac
  2. Start Docker Desktop and try and use the GUI
@nicks
Copy link

nicks commented Aug 31, 2022

Thanks for reporting. I know at least one docker desktop engineer has been using it regularly with the macos Ventura beta. That variable might be a red herring. DD 4.12 will be out soon and I want to double check if this persists for you in 4.12.

@zimmix
Copy link

zimmix commented Sep 1, 2022

Version 4.11.1 (84025)
Diagnostic ID: 44DFBA1F-0514-441F-8AA9-0D19F0DB8B6C/20220901030936

I am no longer able login into AWS ECR from my MacBook Air M2 since I updated to Ventura Beta 6. Login hangs for a while and finally exits with:

Error saving credentials: error storing credentials - err: exit status 1, out: Post "http://ipc/registry/credstore-updated": read unix ->backend.sock: i/o timeout (Client.Timeout exceeded while awaiting headers)

The Docker Desktop reports: It looks like there is an error with Docker Desktop, restart it to fix it. Restarting doesn't fix it.

Also none of the following work:

Clean / Purge data
Reset to factory defaults
Uninstall

Also exiting Docker Desktop hangs.

Re-installation after killing all docker process, deleting the Docker app, and doing: cd ~Library && find . -iname "*docker*" 2>/dev/null | while read i; do rm -rf $i; done did not fix anything.

@jquick
Copy link
Author

jquick commented Sep 1, 2022

@zimmix I was seeing the same issue with unable to do any of the Troubleshooting (uninstall/purge). I ended up manually nuking using https://stackoverflow.com/a/65468254/1432060 and trying multiple versions. But everything I have tried has the same error. I wonder if you look up the docker logs in console while its running if your having the same

"http://ipc/ping": net/http: HTTP/1.x transport connection broken: malformed HTTP response

@arag0re
Copy link

arag0re commented Sep 1, 2022

same issue here

@jquick
Copy link
Author

jquick commented Sep 1, 2022

@nicks It looks like the new version 4.12.0 fixes this issue! 🥳 🚀

I still have a minor issue with SSO just sitting on

validating credentials...

forever until I kill Docker (web login works fine). But that is a minor issue at the moment.

@eshwen
Copy link

eshwen commented Sep 1, 2022

Same for me. The development build of 4.12.0 appears to be working fine except the "validating credentials" hang after attempting to log in

@koodeau

This comment was marked as off-topic.

@koodeau
Copy link

koodeau commented Sep 1, 2022

For now I had Kubernetes working when first ran Docker Desktop after fresh install but it now fails to start constantly and Desktop app seems to have some previous issues from v4.11.1. At least everything else is working fine, maybe except some settings that don't use actively

@koodeau
Copy link

koodeau commented Sep 1, 2022

I suppose it's not only a Docker Desktop GUI issue here but probably something else is going in the background, I suppose it also has to do something with partial support for Apple Silicon in some parts. But I might be wrong.

@drosskopp
Copy link

I got same Problems. Where can I get the development build of 4.12.0?

@arag0re
Copy link

arag0re commented Sep 2, 2022

version 4.12 fixes the issue for me, thanks guys

@eshwen
Copy link

eshwen commented Sep 2, 2022

@drosskopp #6435 (comment)

@DiegoGiovany
Copy link

DiegoGiovany commented Sep 2, 2022

Still unable to quit docker (need to force close on activity monitor), troubleshooting options not work, uninstall not work...

docker-daemon log still showing malformed http on ping request :

[2022-09-02T14:07:39.457905000Z][com.docker.backend][W] (e05a9003-38) 0c7506a2-BackendCMD C<-S NoResponse GET /ping (18.875625ms): Get "http://ipc/ping": net/http: HTTP/1.x transport connection broken: malformed HTTP response "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00{"serverTime":1662127659454}"
^C

@nicks
Copy link

nicks commented Sep 2, 2022

hooray! I'm going to mark this as fixed in 4.12. There's a separate issue for the more narrow credentials issue: #6469

@Dids
Copy link

Dids commented Sep 5, 2022

What exactly does 4.12 fix in relation to this/Ventura issues? Because I'm still seeing all of these issues, even on 4.12, where virtually every action done through the desktop/dashboard app does nothing, including restarting, resetting and shutting down Docker.

@kaorihinata
Copy link

@Dids Nothing, that I can tell. After a period of time the backend becomes unresponsive, and any action that requires communication with the backend ceases to function (like the "Sign In" button, checking for updates, etc), but even before that, checking for updates doesn't function for me. I've tried killing and restarting all Docker processes, I've tried removing Docker, and wiping all traces of it from $HOME/Library, and nothing seems to help. For the people for whom it appears to be working, I wonder if it actually is or if it only appears to be because their backend is so far gone that it's just no longer resulting in an error.

@jedisct1

This comment was marked as off-topic.

@arag0re
Copy link

arag0re commented Sep 11, 2022

What exactly does 4.12 fix in relation to this/Ventura issues? Because I'm still seeing all of these issues, even on 4.12, where virtually every action done through the desktop/dashboard app does nothing, including restarting, resetting and shutting down Docker.

Yes restarting, stopping and all this stuff is still scuffed.

@kaorihinata
Copy link

With macOS Ventura Developer Beta 7 (which is, I think, Public Beta 5?) which just dropped yesterday, it looks like communication with the backend daemon is now fixed, and for me this finally fixed restarting, signing in, most of the stuff in the debug menu, etc. It also seems to have fixed docker login (and by extension, docker-credential-desktop) on the command line (which I believe is the cause of #6469.) Is anyone on Beta 7 still having these issues?

@LorenzoS92
Copy link

LorenzoS92 commented Sep 12, 2022

I confirm that right now the situation seems restored with Beta 7 (Public Beta 5).
No more issues with the communication with backend.
Also from console logging, no more strange errors of ipc/ping.

So, everything ok.

@Dids
Copy link

Dids commented Sep 13, 2022

Worked sporadically for me on the latest macOS Ventura beta at first, but now Docker is refusing to even start. Just stuck starting, and terminating all Docker processes doesn't help, even though this used to help at least get it started.

Surely I'm not the only one who is still seeing issues with Docker for Mac on macOS Ventura?

@arag0re
Copy link

arag0re commented Sep 13, 2022

Worked sporadically for me on the latest macOS Ventura beta at first, but now Docker is refusing to even start. Just stuck starting, and terminating all Docker processes doesn't help, even though this used to help at least get it started.

Surely I'm not the only one who is still seeing issues with Docker for Mac on macOS Ventura?

I had to reinstall it completely, then it was starting.

@kaorihinata
Copy link

Worked sporadically for me on the latest macOS Ventura beta at first, but now Docker is refusing to even start. Just stuck starting, and terminating all Docker processes doesn't help, even though this used to help at least get it started.

Surely I'm not the only one who is still seeing issues with Docker for Mac on macOS Ventura?

Same as @arag0re, I have essentially wiped Docker entirely a few times for this pair of tickets, and am relatively stable for now. Unfortunately, I use Docker as little as possible (just for image building and pushing from the CLI), so I recognize that I may not be especially representative of those with more complicated use cases where you can't just wipe to solve problems.

@sanarena
Copy link

sanarena commented Sep 15, 2022

I am having this issue in 4.12.0. here is the diagnosis ID 0DE2584C-17A4-4359-9A11-365C5C43E538/20220915081442
I did complete wipe and issue did not go away

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Oct 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests