From: Nayana <1880518@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1880518] Re: issue while installing docker inside s390x container
Date: Thu, 18 Mar 2021 10:59:28 -0000 [thread overview]
Message-ID: <161606516890.18172.4816963382658290402.malone@soybean.canonical.com> (raw)
In-Reply-To: 159039304634.8018.14704731502559290875.malonedeb@gac.canonical.com
docker not starting inside s390x container. Log shows:
Error starting daemon: Error initializing network controller: error obtaining controller instance: failed to create NAT chain DOCKER: iptables failed: iptables -t nat -N DOCKER: iptables v1.6.1: can't initialize iptables table `nat': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
(exit status 3)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1880518
Title:
issue while installing docker inside s390x container
Status in QEMU:
Incomplete
Bug description:
This is in reference to https://github.com/multiarch/qemu-user-static/issues/108.
I am facing issue while installing docker inside s390x container under qemu on Ubuntu 18.04 host running on amd64.
Following are the contents of /proc/sys/fs/binfmt_misc/qemu-s390x on Intel host after running
docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
enabled
interpreter /usr/bin/qemu-s390x-static
flags: F
offset 0
magic 7f454c4602020100000000000000000000020016
mask ffffffffffffff00fffffffffffffffffffeffff
I could get docker service up with the following trick.
printf '{"iptables": false,"ip-masq": false,"bridge": "none" }' > /etc/docker/daemon.json
But even though docker service comes up, images are not getting pulled, docker pull fails with the following error.
failed to register layer: Error processing tar file(exit status 1):
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1880518/+subscriptions
next prev parent reply other threads:[~2021-03-18 11:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 7:50 [Bug 1880518] [NEW] issue while installing docker inside s390x container Rajas Kakodkar
2020-05-25 14:36 ` [Bug 1880518] " Laurent Vivier
2020-05-26 7:37 ` Rajas Kakodkar
2021-03-16 11:50 ` Nayana
2021-03-16 12:00 ` Nayana
2021-03-17 16:15 ` Thomas Huth
2021-03-18 9:28 ` Nayana
2021-03-18 10:59 ` Nayana [this message]
2021-03-19 6:54 ` Thomas Huth
2021-03-23 10:53 ` Nayana
2021-04-01 12:00 ` Nayana
2021-04-01 15:21 ` Laurent Vivier
2021-04-23 7:27 ` Nayana
2021-04-29 14:59 ` Nayana
2021-04-30 7:27 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=161606516890.18172.4816963382658290402.malone@soybean.canonical.com \
--to=1880518@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).