Docker not working at all - exit code 139 #3258
Comments
|
@SaturnusDJ And there should be log files in There was an external issue with Docker on ARMv6: #3128 |
|
Reboot: 14:47. Output:
Docker inspect for the container: No logs found in /mnt/dietpi_userdata/docker-data/containers/. Note, this was on the other Docker version I installed to try: No fix:
|
|
Hmm actually I can't see any error, just some warnings about expected skipped modules. Also the status shows an exit code but no error. Not sure what is expected as hallo world output, most likely a console print, that is missing in your case? But did you try an actual docker image/container that is not just for testing purpose? EDIT: Ah sorry you mentioned in OT that exit code 139 is result of others as well. So we need to check what this means. |
|
@MichaIng How about that What I saw in a test yesterday is that the memory starts to get filled until |
|
Docker 139 seems to be container segmentation fault. Could be memory related or due to wrong architecture or many other reasons... Did you take care to pull RPi or armv6hf containers/images. A usual issue is that RPi1/Zero user take regular armhf images which are not compatible with the special armv6hf that RPi1 and Zero is. Also 30 MB left memory is much too few, although hello world should never require that much. However they to increase the swapfile size in case. |
|
For the arch I let it auto select. According to Docker pages it should download the right arch automatically. But...hello-world does not seem to have a So I am trying to verify if I got the right ARM version arch but Docker seems not to show that, or I need a more advanced command. Comparing SHA256 also seems useless? EDIT |
|
@SaturnusDJ
So RPi1/Zero always need special builds, which have neither a clear uname arch print, nor a clear APT architecture. Jep the issue you linked fits, only my state that "armhf fits always" is wrong 😅. |
|
Thank you very much for the explanation! To get Alpine on an RPi 1B, you could run I guess in the case of Portainer they made an ARM image that runs on all versions. https://hub.docker.com/r/portainer/agent/tags And I just checked for the software I used months ago on that RPi 1B, and...no surprise...it is ARM general. That's why it ran. So there is arm32v5, arm32v6, arm32v7, arm64v8 and just 'arm'. Opened this topic for not being able to pull arch + username: https://forums.docker.com/t/how-to-docker-pull-architecture-and-username/85629. Offtopic: |
|
@SaturnusDJ Aside of that, I do not use Docker myself, hence are not expert on anything that goes beyond the general architecture binary compatibility, especially the Docker-specific naming of those. |
|
Thanks @MichaIng, I will stick to pulling and building specifics then. 👌 |
Creating a bug report/issue
Required Information
DietPi version |
cat /DietPi/dietpi/.versionG_DIETPI_VERSION_CORE=6
G_DIETPI_VERSION_SUB=26
G_DIETPI_VERSION_RC=3
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
Distro version |
echo $G_DISTRO_NAMEorcat /etc/debian_version9.11
Kernel version |
uname -aLinux RPi_1B 4.19.66+ DietPi-Config | CPU performance benchmark #1253 Thu Aug 15 11:37:30 BST 2019 armv6l GNU/Linux
SBC device |
echo $G_HW_MODEL_DESCRIPTIONor (EG: RPi3)RPi B (armv6l)
Power supply used | (EG: 5V 1A RAVpower)
5V thing that always worked.
SDcard used | (EG: SanDisk ultra)
2GB thing that always worked.
Additional Information (if applicable)
Docker
Was the software title installed freshly or updated/migrated?
Both. Not sure what the version of the old install was.
Can this issue be replicated on a fresh installation of DietPi?
Yes. Never had this problem. Then after not using this specific RPi for some months, used it again today: problem. Reinstalled DietPi, still problem.
Problem
Most Docker containers exit with code 139. Very difficult to find any errors and logs. Portainer Agent is the only one so far that works.
I tried:
Journalctl -xe during hello-world:
No fix:
Similar (?):
Edit: Did a third install on a different 2GB card (don't have bigger available), this time only installed docker and ran
docker run hello-world. Outcome is the same. Nothing is given as output.docker container ls -ashows exit 139 again.The text was updated successfully, but these errors were encountered: