How to resolve Docker Error Code 132

Docker Engine General
1

Hi,

I have an embedded device where I installed docker. I cannot get any kind of container to run.

docker run --rm -it busybox

Every container exists with 132. No logs, no hints. Probably there is sth wrong with the architecture.

Processor model name: ARMv7 Processor rev 0 (v7l)
Pulled images: "Architecture": "arm", Variant": "v7", Os": "linux",

How can I find out if I’m using the correct image, if I’m missing something on my system or if I have any other issue?

2

What embedded device, which OS, how did you install Docker?

3

I’m using OpenWrt

Linux version 6.6.69 (builder@buildhost) (arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 13.3.0 r28511-c9ae39b2d1) 13.3.0, GNU ld (GNU Binutils) 2.42) #0 SMP Sat Jan 4 19:35:48 2025

Docker version 27.3.1, build ce12230

I have used the manual of OpenWrt: [OpenWrt Wiki] OpenWrt as Docker container host

BTW - the hello world is running without any issues:

docker run hello-world

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (arm32v7)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
 https://hub.docker.com/

For more examples and ideas, visit:
 https://docs.docker.com/get-started/
4

Docker does not support OpenWrt, see doc. You installed a customized version, which is not supported here on the forum. I would consider OpenWrt an embedded Linux, but Docker was mainly build for regular Linux. You probably need to post you question on an OpenWrt forum.

Most regular Docker images are not build with low-level ARM processors in mind. Also OpenWrt is using musl as standard Linux API, which is a “lightweight” set of the standard glibc, so that might have an impact, too.

5

Then it is probbaly not able to open an interactive shell. Or there is an incompatibility in a common library, but the hello-world image contains only a single binary so it is easy to run anywhere.

Just to make sure it is not a general issue on ARM CPUs, I tried it on my Mac and it worked, so as @bluepuma77 suggested, please report this on an OpenWRT forum as well.

To see if it is an issue with the shell, you can try to run this command:

docker run -d --name busyboxtest busybox

And check if it exited with an error code:

docker ps -a
6

I think it is an issue which comes with different images. I have tried a basic alpine image - same.
Probably there is really a library issue that is not working together with the processor.

I anyways wont have much success to get it running with existing Docker images, this is why I probably need to give up here…

7

Have you tried what I suggested? My point was that an intractive shell itself could cause aproblem. If it were a library in the container, the container would at least start and you would see a log message.

8

Yes sorry, forgot to mention that:
Yes I have tried that. The container exits with 132. There is no log at all.

For another container I have got some output rare before exiting with error 132:

stdout: Using path '/opt/app/data' for data