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
Updated Docker, Now Doesn't Work #5037
Comments
This is happening to me as well. I can't even
|
OSX here (10.15.7) and get the "Failed to ping backend API" error. Resetting Docker just hangs it and you have to force quit the application. Was working prior to latest update. |
I uninstalled Docker and reinstalled it and it seems like it is working again. Something must have gone wrong in the update. |
Update: I reinstalled an older version of Docker Desktop and it now launches. Apparently the latest update doesn't support my MacOS version (10.13.6 High Sierra), only 10.14 and up. |
|
same issue, mojave 10.14.6 Dialog displays: Fatal Error Failed to ping backend API From the console log, filtering on "Docker"
|
more info on signatures / authorization from taccy: App path: /Applications/Docker.app Usage Descriptions: Entitlements: App signature check: codesign check: from signet: Code signature scan of all bundles in the folder /Applications/Docker.app: /Applications/Docker.app/Contents/Frameworks/Sparkle.framework/Versions/A/Resources/Autoupdate.app is Notarized. Found 4 bundle signing errors out of 31 scanned in /Applications/Docker.app |
Same issues here with Failed to ping backend API Then when you try to Diagnose & Feedback it just beach balls. So frustrating. |
same here. Uninstall, reinstall, reboot, reset docker to factory defaults doesn't work. macOS 10.15.7 |
same here too. |
Same here, 10.15.7 MacOS |
Same issue here, any updates, please? |
luispcosta, I was only able to relaunch Docker by installing a previous version (used one from last year, when I knew it was working). I haven't tried updating since. |
Tried Edge yesterday. Rebooted and everything. Still not working. |
@asor12 that's what I ended up doing as well. Not a solution though... |
I had this problem, and appeared to get past it? I ran After doing this, I dragged in the latest stable, non-edge Docker.app and ran it, it installed the networking tools and started working again. |
Running Docker version 19.03.13 on macOS Catalina, version 10.15.7 I had this problem today after my computer attempted to update its OS the previous night. The computer couldn't update because an app failed to close (got stuck on the "save your work" prompt). Updated successfully after I closed it. On reboot, Docker threw the "Failed to ping backend API" error when I tried to open Docker Desktop. It hanged when I tried to close it. Since rebooting didn't help, I thought it could have been a permissions issue (I was messing with permissions when I was configuring file sharing). First, I killed the hanging process using I tried starting Docker Desktop again and it worked. |
^ This was my issue too. Thanks! |
My fix was similar - my Mac mysteriously booted me to the login screen out of the blue (maybe to apply a system update?) and when I logged back clicking the Docker Desktop dashboard did nothing. After seeing @tsclay 's post, I did |
Saw this issue on MacOS 10.14.6 with Docker Desktop Version 2.5.0.1. After updating Docker to version 3.0.4 it works again! Thank you guys |
So for those having backend issues, try running version 2.4.0.0 -- https://docs.docker.com/docker-for-mac/release-notes/#docker-desktop-community-2400 I had to revert back to this version in order for Docker to start and work again. Seems that between 2.4.0.0 and the 2.5 versions - something broke. |
I am experiencing this same issue as well. Every time I restart my computer, I get the "Fatal Error - Failed to ping backend API" error. As others have said, clicking "Diagnose & Feedback" just beachballs. Oddly, I have found if I click "Exit" and then go back to Applications and launch Docker again, it seems to work. But if I click "Diagnose & Feedback", and it beachballs, I cannot force quit by CMD-OPT-ESC; as Docker doesn't show there. I have to bring up the Activity Monitor, and find Docker there, and from there, I can force quit. |
@Valien reverting to 2.4.0.0 doesn't seem to be the answer. The update to 2.4.0.0 is where problems first cropped up. |
Ah, missed that. I was going back version by version till I found one that worked and 2.4 is where mine started working again. So wish there was a better option (Podman anyone) for OSX users. :( |
i had this also — what was worse, i'm on Mac OS, and i had that so i opened a terminal and went to the command line, and tried doing what suggested above, running so i remembered — "hey, i'm on Mac OS — i have the activity monitor (which is like command line unix/linux So Docker is running fine now. I'll check back in if, on restart, i get the This is on an older circular black 'trash can' Mac Pro with Mac OS Big Sur v11.2.1, and Docker for Mac OS with Docker Desktop v3.1.0(51484), Engine v20.10.2, Compose v1.27.4, Kubernetes v1.19.3, Notary v0.6.1, Credential Helper v0.6.3 and Smyk v1.432.0. |
I was getting this Updating my Operating System to the latest version worked. Was on Mac 10.3 and updated to Big Sur 11.2 Good luck |
If anyone stumbles upon this and can't click on anything on the GUI and also can't uninstall docker using terminal:
~/Library/Cookies/com.docker.docker.binarycookies is different in that Cookies has extra permissions to it (something bout Apple Quarantine) so I didn't bother touching it. After doing all that and a reinstall of Docker Desktop I was able to launch it where I also clicked uninstall on the UI, so that if I missed any other files it would just do it itself, then I did a fresh install of Docker Desktop once again. Tedious shit for enterprise grade software really MacOS 11.4 |
I just had this error on Docker for Mac 3.4.0, the latest as time of writing, in case anyone thinks it's been fixed since the original report. |
3.4.0 works reliably for me. To get 3.6.0 to work at all I have to |
The issue is not fixed yet on latest "big sur" almost one year later. |
Also curious on when this issue will be finally resolved? I can't always delete my containers, to spin up docker and reimport all my volume data... Can this issues be PRIORITISED over anything, we don't need new feature releases... this is a very CRITICAL bug to be honest. |
Yes exactly... which shouldn't be the case, as all your volumes are gone too. |
While we wait for an update, my workaround is just killing all Docker processes and restart Docker again:
|
|
Facing same issue, I have tried updating OS, reset docker, reboot nothing works. Its always show beach ball everytime I start docker. Please follow below steps for quick work around (not a solution) :
Looking forward for a permanent solution! |
a lot of people with the same issue, why not do a debug and see what is really happening instead of posting shitty workarounds ? |
Guys who upgraded recently to Big Sur or Catalina, there's an OS security model change that requires to assign permissions to docker for file & folders. During startup, docker could fail before asking for permission, if so just do it manually from "System Preferences", then in Privacy tab, Add docker app to Files & Folders & Full Disk access. then it should work fine. |
We just had issues with the It seems to be caused by the name of the homefolder (which was the user´s email-adress, myname@mycompany.com). Changing the home-folder to somthing simpler solved the problem. See guide here about how to do it: https://support.apple.com/en-us/HT201548 (To verify that this is the issue before changing, try creating a new super-user with a simple name, and install/start docker from there) |
Hello, I'm a colleague of @simdadim above 👋 . We just installed Docker Desktop on another Mac which had |
But why would a work for older docker versions then? |
Those workaround with killing docker might work for some, not for everyone, so NOT a solution. No fresh Catalina updates or anything here, permissions are all okay and set for Docker |
This might work but for the 100th of time, SHITTY workaround, since this does delete all containers... so all my databases I can go and re-import. What a time consuming waste of time basically. And if this happens in a current working project, where you did database changes you can do it all over again. DOCKER FOR MAC TEAM, PLEASE LOOK INTO THIS ISSUE AND STOP IGNORING IT! I'm wondering if should start sending client bills your ways? As there is no shame in charging us for certain features. |
@michtio Even if it is a shitty workaround at least I can go and work again. So thanks for this steps! |
Having this problem from last 4 months. could someone from Miriantis/Docker help fix this ? |
Thank you so much. These instructions solved the problem for me. i am finally able to use Docker on my office mac |
I had this error (macOS Monterey 12.0.1). I viewed messages in Console.app when starting Docker and saw some messages (from com.docker.backend, I think, or some other Docker service):
Turned out, these files had bad ACLs on them, and after removing the ACLs with |
Yeah you're right in a way... but if you have 10 projects you have to switch between and all sync and download database again, it feels really cumbersone ... Especially for an enterprise grade solution. |
This is amazing! Well done 👏🏻 Thank you SOOOO much! |
cd ~/Library/Group\ Containers/group.com.docker After search for a full day. This finally work for my m1max. I transfer the docker from intel mac, and download a new version. But it may detect my cpu with intel. So it doesn't tell anything but keep sending GET/ping error After I try the command. It give me the error to say I install the inter version. |
Issues go stale after 90 days of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
I got the same issue, reset to factory setting doesn't work since it didn't finish its job removing all the config files. |
Closed issues are locked after 30 days of inactivity. 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. |
Expected behavior
Launch Docker Desktop
Actual behavior
Returns Fatal Error:
one of the sub-processes failed: com.docker.driver.amd64-linux -addr fd:3 -debug (pid: 13208)
Furthermore, Diagnostics is not working either.
Information
I installed the latest update from Docker Desktop as prompted when opening the app. Now it gives me this Fatal Error when launching:
one of the sub-processes failed: com.docker.driver.amd64-linux -addr fd:3 -debug (pid: 13208)
How do I fix this? Can I go back to the previous Docker Desktop version I was using?
Diagnostic logs
I tried to run Diagnostics but it just stalls.
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: