All versions after 4.15 contain a communication bug between the host and Docker

[budarin]

• [x ] I have tried with the latest version of Docker Desktop
• [x ] I have tried disabling enabled experimental features
• [x ] I have uploaded Diagnostics
• Diagnostics ID: F01C1D4B-2C0C-49A7-87DB-D4CEDD0DBEA4/20230201172550

Expected behavior

everything to work as in version 4.15

Actual behavior

I install new versions, launch my containers as before and try to access them as before - there is no connection

I delete new versions - I put 4.15 and everything works

Information

• macOS Version: Monterey 12.6.3
• Intel chip or Apple chip: Intel
• Docker Desktop Version: 4.16.3

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

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0038: is the connection to Docker working?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0032: do Docker networks overlap with host IPs?
No fatal errors detected.

Steps to reproduce the behavior

docker-stack.zip

I have to stay on version 4.15 for now

[ivuorinen]

Ran into the same problem after upgrade and reverting to 4.15 everything started working again.

[GuillaumeRossolini]

@budarin I had a similar issue on Windows this week, I didn't look to repair anything but essentially, uninstalling docker desktop, rebooting and reinstalling docker desktop did the trick.
I heard about the issue on macOS in one instance and the same process wasn't sufficient, but instead, running docker system prune seems to have fixed that setup.

[budarin]

@budarin I had a similar issue on Windows this week, I didn't look to repair anything but essentially, uninstalling docker desktop, rebooting and reinstalling docker desktop did the trick. I heard about the issue on macOS in one instance and the same process wasn't sufficient, but instead, running docker system prune seems to have fixed that setup.

Thanks for the information, but it will be time-consuming for me to recreate volumes with saved information.
New versions are not critical for me - I'll wait for bug fixes

[djs55]

@budarin thanks for the report.

I install new versions, launch my containers as before and try to access them as before - there is no connection

How are you accessing your containers? Is it via a URL like http://localhost:80 in your browser? Are all ports broken or only some of them?

[budarin]

from browser and CLI

[GuillaumeRossolini]

@djs55 in my case, they were all down (network wise), but I was able to open a shell

I could run docker service ls and see their listening ports as expected, but I could not network into them, or from inside theim to the outside

[budarin]

For example, I expose Grafana ports and at http://127.0.0.1:2000 had access to Grafana
After upgrading - receive ERR_CONNECTION_REFUSED

[budarin]

I have the same bug with new versions of Docker Desktop in Windows

[wp4nuv]

OMG.. and I thought I was going crazy! Thanks for the notice; I thought I was alone with my network problem..

[noahnu]

I can confirm this bug is still present in docker desktop for mac v4.17.0 with mac Ventura (arm64).

[docker-robot]

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 30 days.

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

/lifecycle stale

[derhuerst]

It seems like I'm having this problem too.

• [x ] I have tried with the latest version of Docker Desktop
• [x ] I have tried disabling enabled experimental features
• [x ] I have uploaded Diagnostics (ID: D7939811-1CDB-46F3-B668-C0FC202668BA/20231213121615)

Information

• macOS Version: Ventura 13.6.1
• Intel chip or Apple chip: Apple Silicon M2 (Mac14,2)
• Docker Desktop Version: 4.26.0

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

Starting diagnostics

[2023-12-13T12:17:29.823064000Z][com.docker.diagnose.ipc][I] ipc.NewClient: f1e1c0d4-diagnose -> <HOME>/Library/Containers/com.docker.docker/Data/backend.sock BackendAPI
[2023-12-13T12:17:29.823528000Z][com.docker.diagnose.ipc][I] (7d161141) f1e1c0d4-diagnose C->S BackendAPI POST /idle/make-busy
[2023-12-13T12:17:29.824610000Z][com.docker.diagnose.ipc][I] (7d161141) f1e1c0d4-diagnose C<-S c08a3ff4-BackendAPI POST /idle/make-busy (1.076375ms): 0x140003f4388
[2023-12-13T12:17:30.824639000Z][com.docker.diagnose.ipc][I] (cccd355f) f1e1c0d4-diagnose C->S BackendAPI GET /idle
[2023-12-13T12:17:30.827850000Z][com.docker.diagnose.ipc][I] (cccd355f) f1e1c0d4-diagnose C<-S c08a3ff4-BackendAPI GET /idle (3.033291ms): {"apisInFlight":{"/v1.43/containers/3b98747a1240c466d754723f8755bf0e6d331c6b1c6315702cea5a29f710d4fe/attach":1,"/v1.43/containers/3b98747a1240c466d754723f8755bf0e6d331c6b1c6315702cea5a29f710d4fe/wait":1},"booted":true,"busyReason":["1 container(s)","in-flight APIs: map[/v1.43/containers/3b98747a1240c466d754723f8755bf0e6d331c6b1c6315702cea5a29f710d4fe/attach:1 /v1.43/containers/3b98747a1240c466d754723f8755bf0e6d331c6b1c6315702cea5a29f710d4fe/wait:1]","timed activities: map[/idle/make-busy:28.997949s]"],"containers":1,"idle":"bool","kubernetesEnabled":false,"reduced":false,"services":0,"timedActivities":{"/idle/make-busy":"float64"},"vmPaused":false,"vmRunning":true,"vmStopped":false,"windowsContainers":false}
[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0038: is the connection to Docker working?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[SKIP] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0032: do Docker networks overlap with host IPs?
No fatal errors detected.

Steps to reproduce the behavior

1. install & run Docker Desktop for Mac
2. docker run --rm -it -p 1234:80 caddy
3. curl 'http://localhost:1234' -I (gives "curl: (7) Failed to connect to localhost port 1234 after 0 ms: Couldn't connect to server")