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 Rosetta lock-up while accessing /dev/mem #7512

Open
mdkent opened this issue Dec 20, 2024 · 1 comment
Open

Docker Desktop Rosetta lock-up while accessing /dev/mem #7512

mdkent opened this issue Dec 20, 2024 · 1 comment

Comments

@mdkent
Copy link

mdkent commented Dec 20, 2024

Description

Running dmidecode under Rosetta in a very simple Ubuntu 24.04 container locks up Docker Desktop.

Reproduce

  1. While on an M Series Mac, run
    docker run --platform linux/amd64 --privileged -it ubuntu:24.04 \
      /bin/bash -c 'apt-get update && apt-get -y install dmidecode && dmidecode'
    
    This will never return.
  2. Any other docker command will timeout and fail with request returned Internal Server Error for API route <snip>
  3. The Desktop UI is still running, but attempts to control the containers will see HTTP code 500 errors.

Expected behavior

The command should not hang indefinitely under Rosetta.

The arm64 version of the same image works fine:

docker run --platform linux/arm64 --privileged -it ubuntu:24.04 \
  /bin/bash -c 'apt-get update && apt-get -y install dmidecode && dmidecode'

producing

<snip>
Unpacking dmidecode (3.5-3ubuntu0.1) ...
Setting up dmidecode (3.5-3ubuntu0.1) ...
# dmidecode 3.5
# No SMBIOS nor DMI entry point found, sorry.

It's also worth noting that an older Ubuntu 22.04 release, with an older copy of dmidecode, works fine on amd64:

docker run --platform linux/amd64 --privileged -it ubuntu:22.04 \
  /bin/bash -c 'apt-get update && apt-get -y install dmidecode && dmidecode'

producing

<snip>
Unpacking dmidecode (3.3-3ubuntu0.2) ...
Setting up dmidecode (3.3-3ubuntu0.2) ...
# dmidecode 3.3
Scanning /dev/mem for entry point.
# No SMBIOS nor DMI entry point found, sorry.

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/mkent/.docker/cli-plugins/docker-ai
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.19.2-desktop.1
    Path:     /Users/mkent/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.31.0-desktop.2
    Path:     /Users/mkent/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.37
    Path:     /Users/mkent/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Beta) (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/mkent/.docker/cli-plugins/docker-desktop
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/mkent/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.27
    Path:     /Users/mkent/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/mkent/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.0
    Path:     /Users/mkent/.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/mkent/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.15.1
    Path:     /Users/mkent/.docker/cli-plugins/docker-scout

Server:
 Containers: 6
  Running: 0
  Paused: 0
  Stopped: 6
 Images: 3
 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: 12
 Total Memory: 7.653GiB
 Name: docker-desktop
 ID: f4f75bde-4ff6-4673-9f44-a122a53f92c0
 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/mkent/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

D9FDE95B-C67E-4D64-A7D7-FACB8E8A7235/20241219235941

Additional Info

I'm having trouble deciding where the problem lies for this one, but it seems like Docker shouldn't be able to 100% lock-up while a guest reads /dev/mem.

@mdkent mdkent changed the title Docker Desktop rosetta lock-up while accessing /dev/mem Docker Desktop Rosetta lock-up while accessing /dev/mem Dec 20, 2024
@fbernier
Copy link

I am also encountering the same symptoms, but unsure if it's the very same root cause. Nonetheless, here's my diagnostic-id: D3089024-FCCB-4D9E-AE02-697878568B5D/20241220050254

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants