Looks like docker in docker for cross architectures is not yet supported in
qemu.
can be closed
--
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 s
Looks like for docker in docker in cross architectures is not yet
supported. if we use -v /var/run/docker.sock:/var/run/docker.sock ,
docker will always run as client in s390x container and server from
amd64.
--
You received this bug notification because you are a member of qemu-
devel-ml, which
Any update?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1893040
Title:
External modules retreval using Go1.15 on s390x appears to have
checksum and ECDSA verification issues
Status in QEMU:
I started looking at the issue.Could reproduce issue with steps mentioned in
comment #4
@David Hildenbrand (davidhildenbrand) could you please let me know what exact
qemu version/image you used? and you followed exact steps as mentioned in
comment #4?
--
You received this bug notification be
Could you please let me know if my understanding is correct? Qemu
doesn't support/have enabled related modules? modprobe?
--
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 in
As we are facing issue with service docker start ( for docker in docker
s390x container under qemu)
time="2021-03-23T07:29:07.645278866Z" level=warning msg="Running modprobe
nf_nat failed with message: ``, error: exec: \"modprobe\": executable file not
found in $PATH"
time="2021-03-23T07:29:07.6
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': iptabl
Yes we have observed the issue with multiarch/qemu-user-static image
v5.2.0-1 and 5.2.0-2
--
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 con
Also same issue observed with docker version 19.03. docker pull command
failing with an error "failed to register layer: Error processing tar
file(exit status 1):"
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad
Any pointers about this issue? Any other steps needs to be followed to
resolve the issue?
--
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 con
10 matches
Mail list logo
