Closed lucasbaile closed 2 years ago
I tried reproducing it but it works for me on:
$ uname -a
Linux sdeziel-lemur 5.13.0-40-generic #45~20.04.1-Ubuntu SMP Mon Apr 4 09:38:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
$ snap list lxd
Name Version Rev Tracking Publisher Notes
lxd 5.1-4ae3604 23001 latest/stable canonical✓ -
[root@testcontainer ~]# podman pull quay.io/centos/centos:stream8
Error: 'overlay' is not supported over zfs, a mount_program is required: backing file system is unsupported for this graph driver
[root@testcontainer ~]# vi /etc/containers/storage.conf
[root@testcontainer ~]# podman pull quay.io/centos/centos:stream8
Trying to pull quay.io/centos/centos:stream8...
Getting image source signatures
Copying blob 4a7e61ebcfec done
Copying blob a0b8f3931ffa done
Copying blob 04f0eb705bff done
Copying blob 1ac891d08dc2 done
Copying config 67daa3fbd6 done
Writing manifest to image destination
Storing signatures
67daa3fbd687e011241a14ec37dc733e19cccc35faf944a0455dc78dbddb9caf
[root@testcontainer ~]#
Closing as this feels more like a support question (running a particular workload on LXD) rather than a bug in the container runtime itself. I'd suggest using https://discuss.linuxcontainers.org where we're also all present and is a better location for such questions as solutions tend to be more visible and better indexed than Github.
Required information
ext4
Issue description
So, I understand the question is a little bit convoluted, but for reasons regarding my CI/CD infrastructure, I'm currently in a situation where I want to build and run podman images inside LXD containers. I'm not trying to use podman on rootless mode, so every podman command is ran as sudo. Running a fresh LXD container using the base image
images:centos/8-Stream
, I install podman and try pulling thequay.io/centos/centos:stream8
podman image, and this pull fails if the current error message:I am aware of this fix/workaround:
/etc/containers/storage.conf
and uncommenting this line:But at this point, I just wanted to understand a little better why this is happening, since I'm not trying to use podman in rootless mode, which is one of the main reasons I believe should cause such issue, and I'm openning this issue here because the same podman image can be pulled perfectly fine in the same host machine.
Steps to reproduce
images:centos/8-Stream
base image:quay.io/centos/centos:stream8
image:Information to attach
dmesg
)lxc info NAME --show-log
)Resources: Processes: 12 Disk usage: root: 1.14GiB CPU usage: CPU usage (in seconds): 25 Memory usage: Memory (current): 617.56MiB Memory (peak): 889.88MiB Network usage: eth0: Type: broadcast State: UP Host interface: veth4f3a3b2d MAC address: 00:16:3e:d8:af:b3 MTU: 1500 Bytes received: 351.33MB Bytes sent: 2.41MB Packets received: 178804 Packets sent: 34966 IP addresses: inet: 10.27.217.72/24 (global) inet6: fe80::216:3eff:fed8:afb3/64 (link) lo: Type: loopback State: UP MTU: 65536 Bytes received: 0B Bytes sent: 0B Packets received: 0 Packets sent: 0 IP addresses: inet: 127.0.0.1/8 (local) inet6: ::1/128 (local)
Log:
lxc testcontainer 20220510165502.672 ERROR utils - utils.c:lxc_can_use_pidfd:1792 - Kernel does not support pidfds lxc testcontainer 20220510165502.672 WARN conf - conf.c:lxc_map_ids:3592 - newuidmap binary is missing lxc testcontainer 20220510165502.672 WARN conf - conf.c:lxc_map_ids:3598 - newgidmap binary is missing lxc testcontainer 20220510165502.673 WARN conf - conf.c:lxc_map_ids:3592 - newuidmap binary is missing lxc testcontainer 20220510165502.673 WARN conf - conf.c:lxc_map_ids:3598 - newgidmap binary is missing lxc testcontainer 20220510165509.488 WARN attach - attach.c:get_attach_context:477 - No security context received
lxc monitor
while reproducing the issue)