Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

SIGSEGV when running with Docker on a Pi Zero

See original GitHub issue

I’m unable to run the latest image on a Pi Zero; it exits every time with status code 139. Here’s my docker version output:

Client: Docker Engine - Community
 Version:           19.03.10
 API version:       1.40
 Go version:        go1.13.10
 Git commit:        9424aea
 Built:             Thu May 28 22:24:06 2020
 OS/Arch:           linux/arm
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.10
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       9424aea
  Built:            Thu May 28 22:18:05 2020
  OS/Arch:          linux/arm
  Experimental:     false
 containerd:
  Version:          1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

_Originally posted by @akonradi in https://github.com/mKeRix/room-assistant/issues/155#issuecomment-637089527_

Issue Analytics

State:
Created 3 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

3reactions

sstratoticommented, Jun 13, 2020

Just want to add a quick comment. By using docker-compose version 2.4, you can specify the platform to pull, so you don’t have to specify a digest.

Example:

version: '2.4'
services:
  room-assistant:
    image: mkerix/room-assistant
    platform: linux/arm/v6

By doing this, it’ll pull the arm/v6 version. HTH someone else, cause I was banging my head all afternoon… @mKeRix - you might want to put a note about this in the docker-compose section of the docs?

2reactions

RomRidercommented, Jun 4, 2020

That’s because Docker selects the image for arm7 and raspberry pi zero is arm6. You’ll need to use directly the digest of the armv6 image unfortunately.

It’s unrelated to room-assistant but related to https://github.com/moby/moby/issues/37647

Top Results From Across the Web

raspberry pi docker daemon gives segmentation fault #6335

I installed docker at my raspberry pi zero w running the latest ... that the docker daemon is not working because of the...

Docker Running On RpiZW does everything but actually ...

Docker Running On RpiZW does everything but actually running container, SIGSEGV - Raspberry Pi Stack Exchange. Stack Overflow for Teams – Start ...

Segmentation Fault in Linux Containers (exit code 139)

The SIGSEGV Linux signal denotes a segmentation violation within a running process. Segmentation errors occur when a program tries to access memory that ......

Docker 17.03 on raspberry pi zero W - General Discussions

I am trying to get docker v17. 03.1 to run on raspberry pi zero W using the deb package here: https://download.docker.com/linux/debian/dists/ ...

Docker Daemon failing to start on Raspberry Pi 1 & Zeros

I tried this on a Pi Zero W with Raspbian Stretch and could not get the proper behavior when running 'docker run hello-world'...