moby: docker - write pipe: bad file descriptor
SOLVED for ppc64le : docker run ppc64le/hello-world
** use appropriate architecture **
Description Docker error : “write pipe: bad file descriptor” on every app that i run !! I’m on power8 ubuntu ppc64el but same error on intel arch … see : http://stackoverflow.com/questions/40022817/docker-write-pipe-bad-file-descriptor
Steps to reproduce the issue: docker run hello-world
Describe the results you received: write pipe: bad file descriptor
Describe the results you expected:
Hello from Docker! This message shows that your installation appears to be working correctly.
To generate this message, Docker took the following steps:
- The Docker client contacted the Docker daemon.
- The Docker daemon pulled the “hello-world” image from the Docker Hub.
- The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading.
- 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 Hub account: https://hub.docker.com
For more examples and ideas, visit: https://docs.docker.com/engine/userguide/
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Client:
Version: 1.12.1
API version: 1.24
Go version: go1.6.2
Git commit: 23cf638
Built: Tue, 27 Sep 2016 12:25:38 +1300
OS/Arch: linux/ppc64le
Server:
Version: 1.12.1
API version: 1.24
Go version: go1.6.2
Git commit: 23cf638
Built: Tue, 27 Sep 2016 12:25:38 +1300
OS/Arch: linux/ppc64le
Output of docker info:
Containers: 9
Running: 0
Paused: 0
Stopped: 9
Images: 1
Server Version: 1.12.1
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 19
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: apparmor
Kernel Version: 4.4.0-43-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: ppc64le
CPUs: 40
Total Memory: 3.811 GiB
Name: ubuntu
ID: A2XW:VDZQ:C4I7:HLDP:26CE:XSNG:HBQU:YX2Z:M6BJ:NLSM:7AQ4:ZHWV
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Insecure Registries:
127.0.0.0/8
Additional environment details (AWS, VirtualBox, physical, etc.): uname -a Linux ubuntu 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 13:45:41 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 27 (9 by maintainers)
@prabhukhanna there is no i686 hello world image at present see https://hub.docker.com/u/i686/ for the available images. As said earlier, we do not support i686 and there is no way to even build it in the official repo at present. If someone wants to add support it could be made to work, but we have not had significant demand, and as you can see there are very few available images.
Just for completeness and to help others using the PINE64, I have the same problem using ubuntu 16.04 on PINE64 arch armhf. I also have the same version of systemd that @rcarmo mentioned above, but for me doing an apt-get dist-upgrade and a reboot did not solve the issue.
I did confirm running docker run armhf/hello-world seems to work.