Docker is not stable on M3 Max with Sequoia 15.2
Description
On my company issued M3 Max Macbook Pro I've been faced with nothing but issues with any attempts to run Docker [Desktop or alternate offerings]. Running with or w/out Rosetta 2 has shown no difference. Running Docker with various virtual machine options is no different. Running with or w/out containerd is no different.
Overall issue has been that the docker service seg faults when pulling down docker base images. When the base image is finally pulled down, building the container fails for various compatibility reasons (format errors). Or the docker service seg faults when trying to build for the native architecture or directly for linux/amd64.
This issue happen when doing a docker compose up -d with my companies configuration or when using images from docker hub.
What I've tried
- Fully removing Docker
- Tried alternate docker offerings from OrbStack
Reproduce
- docker run -it alpine:3
Expected behavior
No response
docker version
Client:
Version: 27.4.0
API version: 1.47
Go version: go1.22.10
Git commit: bde2b89
Built: Sat Dec 7 10:35:43 2024
OS/Arch: darwin/arm64
Context: desktop-linux
Server: Docker Desktop 4.37.1 (178610)
Engine:
Version: 27.4.0
API version: 1.47 (minimum version 1.24)
Go version: go1.22.10
Git commit: 92a8393
Built: Sat Dec 7 10:38:33 2024
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: 1.7.21
GitCommit: 472731909fa34bd7bc9c087e4c27943f9835f111
runc:
Version: 1.1.13
GitCommit: v1.1.13-0-g58aa920
docker-init:
Version: 0.19.0
GitCommit: de40ad0
docker info
Client:
Version: 27.4.0
Context: desktop-linux
Debug Mode: false
Plugins:
ai: Ask Gordon - Docker Agent (Docker Inc.)
Version: v0.5.1
Path: /Users/{username}/.docker/cli-plugins/docker-ai
buildx: Docker Buildx (Docker Inc.)
Version: v0.19.2-desktop.1
Path: /Users/{username}/.docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.31.0-desktop.2
Path: /Users/{username}/.docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.37
Path: /Users/{username}/.docker/cli-plugins/docker-debug
desktop: Docker Desktop commands (Beta) (Docker Inc.)
Version: v0.1.0
Path: /Users/{username}/.docker/cli-plugins/docker-desktop
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: /Users/{username}/.docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.27
Path: /Users/{username}/.docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.5
Path: /Users/{username}/.docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.4.0
Path: /Users/{username}/.docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /Users/{username}/.docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.15.1
Path: /Users/{username}/.docker/cli-plugins/docker-scout
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 27.4.0
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
CDI spec directories:
/etc/cdi
/var/run/cdi
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 472731909fa34bd7bc9c087e4c27943f9835f111
runc version: v1.1.13-0-g58aa920
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
cgroupns
Kernel Version: 6.10.14-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 7.654GiB
Name: docker-desktop
ID: e0483a4b-1123-4411-a431-274e9f1bfa9b
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Labels:
com.docker.desktop.address=unix:///Users/{username}/Library/Containers/com.docker.docker/Data/docker-cli.sock
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
WARNING: daemon is not using the default seccomp profile
Diagnostics ID
DB818675-421F-400F-9C35-F3AA877ED219/20241230074956
Additional Info
Additional information reported to OrbStack
Podman a d kubernets stand alone with a software to manage all as 1password 8 dev
Envoyé à partir de Outlook pour Androidhttps://aka.ms/AAb9ysg
From: Ken Simeon @.> Sent: Monday, December 30, 2024 9:23:24 AM To: docker/for-mac @.> Cc: Subscribed @.***> Subject: [docker/for-mac] Docker is not stable on M3 Max with Sequoia 15.2 (Issue #7515)
Description
On my company issued M3 Max Macbook Pro I've been faced with nothing but issues with any attempts to run Docker [Desktop or alternate offerings]. Running with or w/out Rosetta 2 has shown no difference. Running Docker with various virtual machine options is no different. Running with or w/out containerd is no different.
Overall issue has been that the docker service seg faults when pulling down docker base images. When the base image is finally pulled down, building the container fails for various compatibility reasons (format errors). Or the docker service seg faults when trying to build for the native architecture or directly for linux/amd64.
This issue happen when doing a docker compose up -d with my companies configuration or when using images from docker hub.
image.png (view on web)https://github.com/user-attachments/assets/82b1b917-2312-4ec9-a2b3-7197e98670e4
What I've tried
- Fully removing Docker
- Tried alternate docker offerings from OrbStack
Reproduce
- docker run -it alpine:3
Expected behavior
No response
docker version
Client: Version: 27.4.0 API version: 1.47 Go version: go1.22.10 Git commit: bde2b89 Built: Sat Dec 7 10:35:43 2024 OS/Arch: darwin/arm64 Context: desktop-linux
Server: Docker Desktop 4.37.1 (178610) Engine: Version: 27.4.0 API version: 1.47 (minimum version 1.24) Go version: go1.22.10 Git commit: 92a8393 Built: Sat Dec 7 10:38:33 2024 OS/Arch: linux/arm64 Experimental: false containerd: Version: 1.7.21 GitCommit: 472731909fa34bd7bc9c087e4c27943f9835f111 runc: Version: 1.1.13 GitCommit: v1.1.13-0-g58aa920 docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Client: Version: 27.4.0 Context: desktop-linux Debug Mode: false Plugins: ai: Ask Gordon - Docker Agent (Docker Inc.) Version: v0.5.1 Path: /Users/{username}/.docker/cli-plugins/docker-ai buildx: Docker Buildx (Docker Inc.) Version: v0.19.2-desktop.1 Path: /Users/{username}/.docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.31.0-desktop.2 Path: /Users/{username}/.docker/cli-plugins/docker-compose debug: Get a shell into any image or container (Docker Inc.) Version: 0.0.37 Path: /Users/{username}/.docker/cli-plugins/docker-debug desktop: Docker Desktop commands (Beta) (Docker Inc.) Version: v0.1.0 Path: /Users/{username}/.docker/cli-plugins/docker-desktop dev: Docker Dev Environments (Docker Inc.) Version: v0.1.2 Path: /Users/{username}/.docker/cli-plugins/docker-dev extension: Manages Docker extensions (Docker Inc.) Version: v0.2.27 Path: /Users/{username}/.docker/cli-plugins/docker-extension feedback: Provide feedback, right in your terminal! (Docker Inc.) Version: v1.0.5 Path: /Users/{username}/.docker/cli-plugins/docker-feedback init: Creates Docker-related starter files for your project (Docker Inc.) Version: v1.4.0 Path: /Users/{username}/.docker/cli-plugins/docker-init sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.) Version: 0.6.0 Path: /Users/{username}/.docker/cli-plugins/docker-sbom scout: Docker Scout (Docker Inc.) Version: v1.15.1 Path: /Users/{username}/.docker/cli-plugins/docker-scout
Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 27.4.0 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Using metacopy: false Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 2 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog CDI spec directories: /etc/cdi /var/run/cdi Swarm: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: 472731909fa34bd7bc9c087e4c27943f9835f111 runc version: v1.1.13-0-g58aa920 init version: de40ad0 Security Options: seccomp Profile: unconfined cgroupns Kernel Version: 6.10.14-linuxkit Operating System: Docker Desktop OSType: linux Architecture: aarch64 CPUs: 4 Total Memory: 7.654GiB Name: docker-desktop ID: e0483a4b-1123-4411-a431-274e9f1bfa9b Docker Root Dir: /var/lib/docker Debug Mode: false HTTP Proxy: http.docker.internal:3128 HTTPS Proxy: http.docker.internal:3128 No Proxy: hubproxy.docker.internal Labels: com.docker.desktop.address=unix:///Users/{username}/Library/Containers/com.docker.docker/Data/docker-cli.sock Experimental: false Insecure Registries: hubproxy.docker.internal:5555 127.0.0.0/8 Live Restore Enabled: false
WARNING: daemon is not using the default seccomp profile
Diagnostics ID
DB818675-421F-400F-9C35-F3AA877ED219/20241230074956
Additional Info
Additional information reported to OrbStackhttps://github.com/orbstack/orbstack/issues/1646
— Reply to this email directly, view it on GitHubhttps://github.com/docker/for-mac/issues/7515, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BFTH46FRKLIV2AZVAUIHF4L2ID7HZAVCNFSM6AAAAABULV3VCCVHI2DSMVQWIX3LMV43ASLTON2WKOZSG43DEOBTGQ2DCNY. You are receiving this because you are subscribed to this thread.Message ID: @.***>
Upgrade to version 4.37.2 and still experiencing the same stability issues
- Starting Docker Desktop and the docker engine is stopped
- Restart the docker engine and it stops
- System ideal from other process and
/Library/PrivilegedHelperTools/com.docker.vmnetdis sometime using 100% of a cpu
Step today after the udpate
- Cleared out .
dockerdirectory - Cleared out ~/Library/... related files & directories
- Performed an
docker compose up -dof one of my pods- The base image download and upon trying to start the container, the docker engine crashed
$ docker compose up -d db
[+] Running 14/14
✔ db Pulled 9.6s
✔ a9773ff1286c Download complete 0.4s
✔ 192e6a1c4d81 Download complete 2.8s
✔ ad787b48d041 Download complete 0.3s
✔ 1b081673d3b2 Download complete 0.9s
✔ 3a7cdb606eca Download complete 0.4s
✔ d3ac9a132b02 Download complete 0.5s
✔ a9fe95647e78 Download complete 2.6s
✔ ee6612d749c3 Download complete 0.4s
✔ cb07c5e066e1 Download complete 2.0s
✔ d643b7c3b7a9 Download complete 2.6s
✔ c01235e2b759 Download complete 7.7s
✔ 69dbf3f8dd64 Download complete 0.5s
✔ ebdca8197412 Download complete 0.5s
[+] Running 3/3
✔ Network ripp-core_default Created 0.0s
✔ Volume "ripp-core_postgres_data" Created 0.0s
✔ Container ripp-core-db-1 Started
This limiter event is still getting triggered
Event: cpu usage
Action taken: none
CPU: 90 seconds cpu time over 101 seconds (89% cpu average), exceeding limit of 50% cpu over 180 seconds
CPU limit: 90s
Limit duration: 180s
CPU used: 90s
CPU duration: 101s
Duration: 100.99s
Duration Sampled: 97.30s (event starts 2.65s before samples, event ends 1.04s after samples)
Steps: 91
Full Log Report
com.apple.Virtualization.VirtualMachine_2025-01-10-083001_kensimeon-MP3.cpu_resource.log
Hi @kensimeon-rm, sorry you're running into this.
Could you please generate a diagnostic and share the ID with us?
Hi @kensimeon-rm, sorry you're running into this.
Could you please generate a diagnostic and share the ID with us?
Thanks for the support @chris-crone. The diagnostics ID is 982FE88D-4CC0-45AC-B7BB-698CFC6AC97B/20250220143445
Currently I'm running Docker Desktop v4.38.0 on MacOS ~~10.3.1~~ 15.3.1
@chris-crone here is a second diagnostics ID from running a single database container and while a restore was taking place.
982FE88D-4CC0-45AC-B7BB-698CFC6AC97B/20250220151343
Wow its been a day. I actually got a docket panic today while trying to build in image. Diagnostic ID: 982FE88D-4CC0-45AC-B7BB-698CFC6AC97B/20250220215021
The saga continues. Since the last update I've totally reinstalled MacOS. Docker was stable for the most part, but I'd still have issues with the docker engine stopping. I took the effort to update our docker files to be less dependent on x86_64 emulation. But when running any docker instances that requires building, everything gets sketchy.
Diagnostics ID: 18F57D45-D726-4FFB-A577-0BC5BF928D42/20250304012606
Thanks @kensimeon-rm, we're taking a look
Previously you said:
Currently I'm running Docker Desktop v4.38.0 on MacOS 10.3.1
I assume you meant macOS 15.3.1?
Yikes! Sorry about that @chris-crone. That was a type-o. Yes, I've always been running MacOS 15.3.x
I continue to have unexpected stoppages of the Docker Engine or full on crashes of Docker Desktop. Lately I've been running version 4.27.2 because a co-work with the same machines has had success with the version. Initially Docker was working more consistently and i was able to build & run containers. However, over just a few days the application stability has drastically declined.
Diagnostics ID: DCF1A43D-FEDD-4E86-B4BB-B70CBB42146F/20250321143527