Updated Docker, Now Doesn't Work

[asor12]

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID: [Diagnostics not working either]

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

• macOS Version: 10.13.6 High Sierra

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

Docker for Mac: version...

I tried to run Diagnostics but it just stalls.

Steps to reproduce the behavior

1. Install latest version of Docker Desktop
2. Try to launch app

[fireynis]

This is happening to me as well. I can't even docker ps or docker container ls it just hangs. When I try to docker build one of my compose file (which worked previously to the update) I get the following:

docker-compose build
Traceback (most recent call last):
  File "site-packages/urllib3/connectionpool.py", line 426, in _make_request
  File "<string>", line 3, in raise_from
  File "site-packages/urllib3/connectionpool.py", line 421, in _make_request
  File "http/client.py", line 1344, in getresponse
  File "http/client.py", line 306, in begin
  File "http/client.py", line 267, in _read_status
  File "socket.py", line 589, in readinto
socket.timeout: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "site-packages/requests/adapters.py", line 449, in send
  File "site-packages/urllib3/connectionpool.py", line 727, in urlopen
  File "site-packages/urllib3/util/retry.py", line 403, in increment
  File "site-packages/urllib3/packages/six.py", line 735, in reraise
  File "site-packages/urllib3/connectionpool.py", line 677, in urlopen
  File "site-packages/urllib3/connectionpool.py", line 428, in _make_request
  File "site-packages/urllib3/connectionpool.py", line 336, in _raise_timeout
urllib3.exceptions.ReadTimeoutError: UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "site-packages/docker/api/client.py", line 205, in _retrieve_server_version
  File "site-packages/docker/api/daemon.py", line 181, in version
  File "site-packages/docker/utils/decorators.py", line 46, in inner
  File "site-packages/docker/api/client.py", line 228, in _get
  File "site-packages/requests/sessions.py", line 543, in get
  File "site-packages/requests/sessions.py", line 530, in request
  File "site-packages/requests/sessions.py", line 643, in send
  File "site-packages/requests/adapters.py", line 529, in send
requests.exceptions.ReadTimeout: UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "docker-compose", line 3, in <module>
  File "compose/cli/main.py", line 67, in main
  File "compose/cli/main.py", line 123, in perform_command
  File "compose/cli/command.py", line 69, in project_from_options
  File "compose/cli/command.py", line 132, in get_project
  File "compose/cli/docker_client.py", line 43, in get_client
  File "compose/cli/docker_client.py", line 170, in docker_client
  File "site-packages/docker/api/client.py", line 188, in __init__
  File "site-packages/docker/api/client.py", line 213, in _retrieve_server_version
docker.errors.DockerException: Error while fetching server API version: UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

[Valien]

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.

[fireynis]

I uninstalled Docker and reinstalled it and it seems like it is working again. Something must have gone wrong in the update.

[asor12]

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.

[Farkal]

I uninstalled Docker and reinstalled it and it seems like it is working again. Something must have gone wrong in the update.

Reset to factory defaults from the troubleshoot menu worked for me

[mcooperman]

same issue, mojave 10.14.6
tried dragging app to trash, as well as ~/Libraries/Application Support/Docker
then re-installing the new docker
then rebooting
then trying to launch the app
Does not correct the problem
hangs on Diagnostics or Reset to Factory Defaults

Dialog displays:

Fatal Error

Failed to ping backend API

From the console log, filtering on "Docker"
a couple of events of note

• [ERROR] Prompting policy for hardened runtime; service: kTCCServiceAppleEvents requires entitlement com.apple.security.automation.apple-events but it is missing for ACC:{ID: com.docker.docker, PID[5270], auid: 607088425, euid: 607088425, binary path: '/Applications/Docker.app/Contents/MacOS/Docker'}, REQ:{ID: com.apple.appleeventsd, PID[72], auid: 55, euid: 55, binary path: '/System/Library/CoreServices/appleeventsd'}
  ...
• starting backend server
• started port-forwarding control server on vpnkit.port.sock
  ...
• LSExceptions shared instance invalidated for timeout.

[mcooperman]

same issue, mojave 10.14.6
tried dragging app to trash, as well as ~/Libraries/Application Support/Docker
then re-installing the new docker
then rebooting
then trying to launch the app
Does not correct the problem
hangs on Diagnostics or Reset to Factory Defaults

Dialog displays:

Fatal Error

Failed to ping backend API

From the console log, filtering on "Docker"
a couple of events of note

• [ERROR] Prompting policy for hardened runtime; service: kTCCServiceAppleEvents requires entitlement com.apple.security.automation.apple-events but it is missing for ACC:{ID: com.docker.docker, PID[5270], auid: 607088425, euid: 607088425, binary path: '/Applications/Docker.app/Contents/MacOS/Docker'}, REQ:{ID: com.apple.appleeventsd, PID[72], auid: 55, euid: 55, binary path: '/System/Library/CoreServices/appleeventsd'}
  ...
• starting backend server
• started port-forwarding control server on vpnkit.port.sock
  ...
• LSExceptions shared instance invalidated for timeout.

more info on signatures / authorization
some of the items in the Docker.app bundle show issus

from taccy:

App path: /Applications/Docker.app
app ID: com.docker.docker
version: 2.5.0.0
build: 49427
SDK version: macosx10.15 ( i am on macosx10.14.6 )

Usage Descriptions:

Entitlements:
com.apple.developer.team-identifier : 9BNSXJN65R
com.apple.security.app-sandbox : 0
com.apple.security.files.user-selected.read-write : 1
com.apple.security.application-groups : (
    "group.com.docker"
)
com.apple.application-identifier : 9BNSXJN65R.com.docker.docker
keychain-access-groups : (
    "9BNSXJN65R.com.docker.docker"
)

App signature check:
/Applications/Docker.app: accepted
source=Notarized Developer ID
override=security disabled
origin=Developer ID Application: Docker Inc (9BNSXJN65R)

codesign check:
Executable=/Applications/Docker.app/Contents/MacOS/Docker
Identifier=com.docker.docker
Format=app bundle with Mach-O thin (x86_64)
CodeDirectory v=20500 size=112317 flags=0x10000(runtime) hashes=3501+5 location=embedded
Hash type=sha256 size=32
CandidateCDHash sha1=cf5d03b3110efb402455523024a3e7732f7f2cbf
CandidateCDHash sha256=699188883ed16d116a54ae2041ba36f931a394e3
Hash choices=sha1,sha256
CDHash=699188883ed16d116a54ae2041ba36f931a394e3
Signature size=9001
Authority=Developer ID Application: Docker Inc (9BNSXJN65R)
Authority=Developer ID Certification Authority
Authority=Apple Root CA
Timestamp=Nov 2, 2020 at 10:04:59 AM
Info.plist entries=46
TeamIdentifier=9BNSXJN65R
Runtime Version=10.15.4
Sealed Resources version=2 rules=13 files=14355
Internal requirements count=1 size=212

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.
/Applications/Docker.app/Contents/Library/LoginItems/DockerHelper.app is Notarized.
/Applications/Docker.app/Contents/MacOS/Docker Desktop.app is Notarized.
/Applications/Docker.app/Contents/MacOS/Docker Desktop.app/Contents/Frameworks/Docker Desktop Helper (GPU).app is Notarized.
/Applications/Docker.app/Contents/MacOS/Docker Desktop.app/Contents/Frameworks/Docker Desktop Helper (Plugin).app is Notarized.
/Applications/Docker.app/Contents/MacOS/Docker Desktop.app/Contents/Frameworks/Docker Desktop Helper (Renderer).app is Notarized.
/Applications/Docker.app/Contents/MacOS/Docker Desktop.app/Contents/Frameworks/Docker Desktop Helper.app is Notarized.
/Applications/Docker.app/Contents/Resources/bin/docker-compose error -67056 code has no resources but signature indicates they must be present
/Applications/Docker.app/Contents/Resources/snyk/docker/cli error getting code 100021
/Applications/Docker.app/Contents/Resources/snyk/docker/node-v12.18.3-darwin-x64/lib/node_modules/npm/node_modules/node-gyp/gyp error -67062 code object is not signed at all
/Applications/Docker.app/Contents/Resources/snyk/docker/node-v12.18.3-darwin-x64/lib/node_modules/npm/node_modules/node-gyp/gyp/samples error -67062 code object is not signed at all

Found 4 bundle signing errors out of 31 scanned in /Applications/Docker.app
Checked at Monday, November 9, 2020 at 11:15:02 AM Eastern Standard Time

[Valien]

Same issues here with Failed to ping backend API

Then when you try to Diagnose & Feedback it just beach balls.

So frustrating.

[Peresh]

Same issue.

macOS Catalina Version 10.15.7
with Docker Desktop stable version for macOS

Reboot, Reinstall doesn't work.
Reset Docker to factory defaults, Diagnose & Feedback ends with no response.

[keo]

same here. Uninstall, reinstall, reboot, reset docker to factory defaults doesn't work. macOS 10.15.7

[stofancy]

same here too.
I tried reset docker to factory defaults, uninstall reinstall, reboot, uninstall and reinstall again, doesn't work. 10.15.7 MacOS.

[arich-medavie]

Same here, 10.15.7 MacOS
I've also tried uninstalling, reinstalling, resetting to factory defaults - all of it doesn't work.

[luispcosta]

Same issue here, any updates, please?

[asor12]

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.

[Valien]

Tried Edge yesterday. Rebooted and everything. Still not working.

[luispcosta]

@asor12 that's what I ended up doing as well. Not a solution though...

[Heanthor]

I had this problem, and appeared to get past it?

I ran /Applications/Docker.app/Contents/MacOS/Docker --uninstall from the troubleshooting steps two or three times, it would hang and sometimes error out with "docker.SettingsError error 2" but it must have done something. I then dragged my old Docker.app to the trash.

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.

[tsclay]

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 top | grep "Docker" then kill <pid here>. Then, I went to my root folder in Finder, made sure permissions for my user were "Read & Write", and that those permissions were applied to items enclosed.

I tried starting Docker Desktop again and it worked.

[arkanath]

^ This was my issue too. Thanks!

[mieubrisse]

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 ps aux | grep -i 'docker' and saw many instances of /Applications/Docker.app/Contents/MacOS/Docker Desktop.app/Contents/Frameworks/Docker Desktop Helper (Renderer).app/Contents/MacOS/Docker Desktop Helper (Renderer) running. I ran osascript -e 'quit app "Docker"' to stop the Docker engine, then I manually ran kill <pid> on all the rogue Desktop Helper processes. I started Docker Desktop back up, and things worked.

[crealistiques]

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

[Valien]

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.

[begrafx]

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.

[begrafx]

@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.

[Valien]

@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. :(

[faddah]

i had this also — what was worse, i'm on Mac OS, and i had that Fatal Error dialogue that had the SPOD (the multi-colored spinning error/buffering wheel, "spinning pizza of death") over it whenever i moved the cursor there, so i couldn't click the troubleshooting buttons or anything, and i'd get the same thing when i'd try to put my cursor over the docker menu in the Mac OS general finder menu bar. what was worse, doing command-key-option-key-escape-key to bring up the running apps and trying to force quit docker, as docker runs in the background, it wasn't shown there. really frustrating.

so i opened a terminal and went to the command line, and tried doing what suggested above, running /Applications/Docker.app/Contents/MacOS/Docker --uninstall several times over. but that just kept retuning the error json error: Error Domain=NSCocoaErrorDomain Code=3840 "No value." UserInfo={NSDebugDescription=No value.}, and it would stay there and i'd have to do ^C to get out of it.

so i remembered — "hey, i'm on Mac OS — i have the activity monitor (which is like command line unix/linux top on steroids with a GUI) which can kill processes. so i searched for every process running for "docker" and it was just the docker background app and the docker desktop which showed as running but not responding (duh!). i quite both of those, went back to my Mac OS Applications, re-ran the Docker app, and it came up and ran fine.

So Docker is running fine now. I'll check back in if, on restart, i get the Fatal Error again. if you don't hear from me, that means on restart Docker runs fine still.

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.

[ecairol]

I was getting this Failed to ping backend API

Updating my Operating System to the latest version worked. Was on Mac 10.3 and updated to Big Sur 11.2

Good luck

[cgarrovillo]

If anyone stumbles upon this and can't click on anything on the GUI and also can't uninstall docker using terminal: /Applications/Docker.app/Contents/MacOS/Docker --uninstall (as said on their official logs and troubleshooting support) I had to manually uninstall all the files through terminal. The files would be

• /Library/PrivilegedHelperTools/com.docker.vmnetd

• /Library/LaunchDaemons/com.docker.vmnetd.plist

• /usr/local/lib/Docker

• ~/.docker

• ~/Library/Containers/com.docker.docker

• ~/Library/Application Support/Docker Desktop

• ~/Library/Preferences/com.docker.docker.plist

• ~/Library/Saved Application State/com.electron.docker-frontend.savedState

• ~/Library/Group Containers/group.com.docker

• ~/Library/Logs/Docker Desktop

• ~/Library/Preferences/com.electron.docker-frontend.plist

• ~/Library/Cookies/com.docker.docker.binarycookies

~/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
Docker Desktop 3.4.0 (2021-06-09)
Intel

[allanlewis]

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.

[ejdunn2001]

3.4.0 works reliably for me.

To get 3.6.0 to work at all I have to rm -rf ~/Library/Containers/com.docker.docker every time I reboot.

[joseluisq]

The issue is not fixed yet on latest "big sur" almost one year later.

[michtio]

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.

[michtio]

3.4.0 works reliably for me.

To get 3.6.0 to work at all I have to rm -rf ~/Library/Containers/com.docker.docker every time I reboot.

Yes exactly... which shouldn't be the case, as all your volumes are gone too.

[juananpe]

While we wait for an update, my workaround is just killing all Docker processes and restart Docker again:

$ pkill Docker

$ /Applications/Docker.app/Contents/MacOS/Docker &

[kiru42]

killall Docker && cd /Applications;open -a Docker;cd ~

[guptajiten]

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) :

1. KILL OLD INSTANCE - pkill -f 'Docker.app'
2. REMOVE - rm -rf ~/Library/Containers/com.docker.docker
3. RESTART - cd /Applications;open -a Docker;cd ~

Looking forward for a permanent solution!

[giondo]

a lot of people with the same issue, why not do a debug and see what is really happening instead of posting shitty workarounds ?

[abarrak]

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.

[simdadim]

We just had issues with the Fatal Error - Failed to ping backend API error. And we solved it:

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)

[emirlej]

We just had issues with the Fatal Error - Failed to ping backend API error. And we solved it:

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 @ in the user name and it worked. So, the root cause is something else 🤷‍♂️ ...

[JonasDoe]

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.

But why would a work for older docker versions then?

[michtio]

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
an @ in the home folder name is also not the solution, as my home folder is michtio so simpler couldn't be.

[michtio]

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) :

1. KILL OLD INSTANCE - pkill -f 'Docker.app'
2. REMOVE - rm -rf ~/Library/Containers/com.docker.docker
3. RESTART - cd /Applications;open -a Docker;cd ~

Looking forward for a permanent solution!

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.

[lucasjahn]

@michtio Even if it is a shitty workaround at least I can go and work again. So thanks for this steps!

[PavanMudigondaTR]

Having this problem from last 4 months. could someone from Miriantis/Docker help fix this ?

[PavanMudigondaTR]

We just had issues with the Fatal Error - Failed to ping backend API error. And we solved it:

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)

Thank you so much. These instructions solved the problem for me. i am finally able to use Docker on my office mac

[sandinmyjoints]

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):

unlocking leaked directory locks: 2 errors occurred:
	* modifying existing entry for /Users/william/scm/sd/sd-playground/config: getting qualifier in ACL entry &{0x13700ba10} for /Users/william/scm/sd/sd-playground/config: mbr_uuid_to_id: No such file or directory
	* modifying existing entry for /Users/william/scm/sd/sd-playground/src: getting qualifier in ACL entry &{0x13800d810} for /Users/william/scm/sd/sd-playground/src: mbr_uuid_to_id: No such file or directory

Turned out, these files had bad ACLs on them, and after removing the ACLs with chmod -N, Docker started up again. I wrote the whole thing up here: Fixing 'Failed to ping backend API' Docker error on macOS .

[michtio]

@michtio Even if it is a shitty workaround at least I can go and work again. So thanks for this steps!

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.

[michtio]

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):

unlocking leaked directory locks: 2 errors occurred:
	* modifying existing entry for /Users/william/scm/sd/sd-playground/config: getting qualifier in ACL entry &{0x13700ba10} for /Users/william/scm/sd/sd-playground/config: mbr_uuid_to_id: No such file or directory
	* modifying existing entry for /Users/william/scm/sd/sd-playground/src: getting qualifier in ACL entry &{0x13800d810} for /Users/william/scm/sd/sd-playground/src: mbr_uuid_to_id: No such file or directory

Turned out, these files had bad ACLs on them, and after removing the ACLs with chmod -N, Docker started up again. I wrote the whole thing up here: Fixing 'Failed to ping backend API' Docker error on macOS .

This is amazing! Well done 👏🏻

Thank you SOOOO much!

[hezll]

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.

cd ~/Library/Group\ Containers/group.com.docker
rm -rf settings.json

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
level="error" msg="IPCClient: 8bcfceb0-GoBackend (0de2c05e) C<-S GET /ping (4.603028ms): Request failed: no response"
time="2021-12-23T13:44:25Z" level="info" msg="IPCClient: 8bcfceb0-GoBackend (794981d0) C->S GET /ping"
time="2021-12-23T13:44:25Z" level="error" msg="IPCClient: 8bcfceb0-GoBackend (794981d0) C<-S GET /ping (4.163980ms): Request failed: no response"
time="2021-12-23T13:44:25Z" level="info" msg="IPCClient: 8bcfceb0-GoBackend (b545081e) C->S GET /ping"
time="2021-12-23T13:44:25Z" level="error" msg="IPCClient: 8bcfceb0-GoBackend (b545081e) C<-S GET /ping (4.415035ms): Request failed: no

After I try the command. It give me the error to say I install the inter version.
So I reinstall Apple chip version. Everything works fine.

[docker-robott]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

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

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.
/lifecycle stale

[hucancode]

I got the same issue, reset to factory setting doesn't work since it didn't finish its job removing all the config files.
I had to find those config files and remove it manually. Thanks cgarrovillo for the list

[docker-robott]

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