Cómo solucionar `docker run` con exit code 1 en Raspberry Pi

This article explains how to resolve the Docker run command returning an exit code of 1 on a Raspberry Pi. The error code 1 signifies that the container's main process terminated due to a generic error.

The most common causes on Raspberry Pi are an architecture mismatch, lack of compatible binaries, permission issues or missing dependencies, and misuse of the --net=host option in certain outdated Docker versions. One key note is that the command docker run --net = host -d -t myimage contains a syntax error due to spaces around the = sign in --net=host, which Docker interprets as a literal network name rather than a flag.

To fix the issue, first correct the command syntax by removing spaces around the = in --net=host: docker run --net=host -d -t myimage. Next, verify the image's architecture by executing docker inspect myimage --format {{.Architecture}} on your Raspberry Pi. If the output is amd64, the image is incompatible with Raspberry Pi (unless using QEMU emulation) and should show either arm or arm64 instead.

If you own the image, rebuild it for ARM architecture using the appropriate Docker build command. Alternatively, download a pre-built compatible image such as arm32v7/python:3.9 or arm64v8/nginx. To debug the container if it has already started, run it in interactive mode with -it to view the error in real-time: docker run --net=host -it myimage. This will display the actual error message (such as exec format error, segmentation fault, or command not found).

If you need to build your own image, ensure the Dockerfile specifies the correct base image for your Raspberry Pi architecture, e.g., FROM arm32v7/python:3.9-slim. Using docker buildx for multi-architecture builds can also help maintain compatibility across different platforms, automatically generating native images for each architecture to avoid exec format errors.

The expected outcome is a successfully running container without exiting with error code 1, allowing you to further debug any other specific issues using the logs in interactive mode.