Open rajaskakodkar opened 4 years ago
What is the host OS? Ubuntu?
I am not sure about the issue. https://stackoverflow.com/questions/44678725/cannot-connect-to-the-docker-daemon-at-unix-var-run-docker-sock-is-the-docker
The docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
installs the following files with flags: F
.
If you can find it.
/proc/sys/fs/binfmt_misc/qemu-$arch
First you can try Travis arch: s390x
, can you do the operation without QEMU in the environment?
Next you can try the following apt package. May it also overrides teh binfmt_misc files.
$ apt-get install -y binfmt-support
If still does not work, it might be QEMU issue. You can ask it on QEMU issue tracker showing your binfmt_misc file
/proc/sys/fs/binfmt_misc/qemu-s390x
What is the host OS? Ubuntu?
Yes, Ubuntu 18.04
/proc/sys/fs/binfmt_misc/qemu-$arch
Contents of this file are
enabled
interpreter /usr/bin/qemu-s390x-static
flags: F
offset 0
magic 7f454c4602020100000000000000000000020016
mask ffffffffffffff00fffffffffffffffffffeffff
First you can try Travis arch: s390x, can you do the operation without QEMU in the environment?
I cannot do without QEMU in the environment
I have reported this bug on qemu issue tracker https://bugs.launchpad.net/qemu/+bug/1880518
Contents of this file are
Sure, this is expected one.
I cannot do without QEMU in the environment
I meant if you use Travis CI's s390x native host feature, you can build and run your s390x Dockerfile
container without QEMU, you can know the error by apt-get install -y --no-install-recommends docker-ce=18.06.*
comes from QEMU or s390x architecture specific.
You can see https://docs.travis-ci.com/user/multi-cpu-architectures/ for detail.
I have reported this bug on qemu issue tracker https://bugs.launchpad.net/qemu/+bug/1880518
Nice! Thank you for that.
I meant if you use Travis CI's s390x native host feature, you can build and run your s390x
Dockerfile
container without QEMU, you can know the error byapt-get install -y --no-install-recommends docker-ce=18.06.*
comes from QEMU or s390x architecture specific.
The error appears on s390x native container, but it does not stop docker from starting. docker in docker works flawlessly on s390x native host. Following trick worked to get docker service up on s390x container under QEMU.
printf '{"iptables": false,"ip-masq": false,"bridge": "none" }' > /etc/docker/daemon.json
but docker pull fails with this error
failed to register layer: Error processing tar file(exit status 1):
I have mentioned this in the bug reported on qemu issue tracker.
This is can be closed as corresponding qemu issue is closed
Is this a bug report, feature (enhancement) request or question? (leave only one on its own line)
/kind bug
Description:
Not able to install docker inside s390x container under qemu on amd64
Steps to reproduce the issue:
docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
docker run --it --privileged s390x/ubuntu:18.04
apt-get update
apt-get install -y \ apt-transport-https \ ca-certificates \ curl \ gnupg-agent \ software-properties-common
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | apt-key add -
add-apt-repository \ "deb [arch=s390x] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) \ stable"
apt-get update
apt-get install -y --no-install-recommends docker-ce=18.06.*
Describe the results you received: These errors are seen while installing docker
docker does not come up after running
service docker start
Describe the results you expected: Docker is expected to come up after running
service docker start
Environment:
Output of
docker version
Additional information optionally: I tried the following fixes before installing docker inside the s390x container but they didn't work.