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

Issue: Segmentation fault on M1 Mac when running docker image #19

Open
PikachuEXE opened this issue Jul 4, 2022 · 2 comments
Open

Issue: Segmentation fault on M1 Mac when running docker image #19

PikachuEXE opened this issue Jul 4, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@PikachuEXE
Copy link

PikachuEXE commented Jul 4, 2022

Env

  • MacBook Pro (14-inch, 2021)
  • MacOS 12.1
  • Docker Desktop 4.10.0 (82025)
`docker info`
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc., v0.8.2)
  compose: Docker Compose (Docker Inc., v2.6.1)
  extension: Manages Docker extensions (Docker Inc., v0.2.7)
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
  scan: Docker Scan (Docker Inc., v0.17.0)

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 11
 Server Version: 20.10.17
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  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 logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1
 runc version: v1.1.2-0-ga916309
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.10.104-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 4
 Total Memory: 3.841GiB
 Name: docker-desktop
 ID: IBXS:EE4X:D3YC:TTQR:H6VP:IOUQ:7KPN:F3YU:Z7X5:KNCI:FE7V:G7GA
 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
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5000
  127.0.0.0/8
 Live Restore Enabled: false

Steps

docker run --rm ghcr.io/blockpane/tenderduty:latest -example-config >config.yml
# or just bash
docker run --rm -it  --platform linux/amd64 ghcr.io/blockpane/tenderduty:latest bash

# Edit 1: The bash command was incorrect before, but after command was fixed it still got the same issue

Outputs

The warning is normal and can be ignored

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
@blockpane
Copy link
Owner

I'll have to look into how to build an arm linux image via github actions, if it's even possible. The m1 docker suite uses qemu and is arm. The published images are the same that the Dockerfile provides, so you should be able to just clone the repo and build the image and get native arm binaries. Much of my dev is on an m1, so I can confirm at least this works.

@blockpane blockpane self-assigned this Jul 4, 2022
@blockpane blockpane added the enhancement New feature or request label Sep 25, 2022
@Kwaskoff
Copy link

no matching manifest for linux/arm64/v8 in the manifest list entries
Why? It's easy to implement! 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants