Docker Community Forums

Share and learn in the Docker community.

Docker error "exec format error"


(Mibellil) #1

Hi all ,
docker version : http://paste.fedoraproject.org/285817/14464087
docker info : http://paste.fedoraproject.org/285813/14464084
docker images : docker.io/busybox latest

when run command i got this error.
Docker Error :
exec format error
Error response from daemon: Cannot start container 03…1e: [8] System error: exec format error

uname -r : 4.2.3-200.fc22.i686

Reinstall it :
docker run busybox

Unable to find image ‘busybox:latest’ locally
Trying to pull repository docker.io/library/busybox … latest: Pulling from library/busybox
d1592a710ac3: Pull complete
17583c7dd0da: Pull complete
library/busybox:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.
Digest: sha256:87fcdf79b696560b61905297f3be7759e01130a4befdfe2cc9ece9234bbbab6f
Status: Downloaded newer image for docker.io/busybox:latest

exec format error
Error response from daemon: Cannot start container f799c27b229a8b38a099dfee3d07345306b568018669a7a87bc00cac141e5950: [8] System error: exec format error

Any help, thank you.


(Mibellil) #3

http://gool.us/d/1446468941781.png


(Jeff Anderson) #4

Hello,

Your uname indicates that you are running a 32-bit kernel. The busybox image is a 64-bit image, which is why you get that error.

The upstream docker project only runs docker on x86_64 hosts. Docker can be run on other architectures, as long as you run images that correspond to the architecture you are using. The official docker images are provided only as 64-bit images.

There are non-official busybox 32-bit images out in the wild. I found a couple by searching ‘busybox32’: https://hub.docker.com/r/mzdaniel/busybox32/ and https://hub.docker.com/r/wtanaka/busybox32/

/Jeff


(Mibellil) #5

Thank you
it’s working now,

http://gool.us/d/1446487337971.png