Your message dated Wed, 21 Apr 2021 22:19:04 +0000
with message-id <e1lzlby-000gwn...@fasolo.debian.org>
and subject line Bug#987207: fixed in libpod 3.0.1+dfsg1-2
has caused the Debian Bug report #987207,
regarding Missing dependency on "iptables"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
987207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: podman
Version: 3.0.1+dfsg1-1
Severity: serious
Hello,
After installing podman, I cannot run it as root out of the box as it
fails with:
ERRO[0000] [graphdriver] prior storage driver overlay failed: kernel does not
support overlay fs: 'overlay' is not supported over extfs at
"/var/lib/containers/storage/overlay": backing file system is unsupported for
this graph driver
Error: kernel does not support overlay fs: 'overlay' is not supported over
extfs at "/var/lib/containers/storage/overlay": backing file system is
unsupported for this graph driver
Looking at fedora it seems that they have a containers-common package
that ships a default storage.conf file:
https://src.fedoraproject.org/rpms/containers-common/blob/rawhide/f/storage.conf
I see that the debian package is shipping a file in
/usr/share/containers/storage.conf (in the containers-storage package),
but that file is apparently not read (strace only shows that the file in
/etc/containers is read) and anyway unlike in fedora:
1) the driver is not set to overlay
2) the file is installed only if the containers-storage package is
installed, which is not done by default.
3) that file is not read anyway, strace only shows that
/etc/containers/storage.conf is read and not
/usr/share/containers/storage.conf, so the file is apparently useless
Shouldn't debian do the same thing than fedora so everything works OOTB?
As a side note, I can see they are shipping also other files as well,
like the seccomp.json file, using strace, it seems that podman tries to
read them:
[pid 14835] newfstatat(AT_FDCWD, "/etc/containers/seccomp.json", 0xc0000ee6b8,
0) = -1 ENOENT (Aucun fichier ou dossier de ce type)
[pid 14835] newfstatat(AT_FDCWD, "/usr/share/containers/seccomp.json",
0xc0000ee788, 0) = -1 ENOENT (Aucun fichier ou dossier de ce type)
Shouldn't that file be shipped by default too?
Kind regards,
Laurent Bigonville
-- System Information:
Debian Release: 11.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
Versions of packages podman depends on:
ii conmon 2.0.25+ds1-1
ii containernetworking-plugins 0.9.0-1+b3
ii golang-github-containers-common 0.35.4+ds1-1
ii init-system-helpers 1.60
ii libc6 2.31-11
ii libdevmapper1.02.1 2:1.02.175-2.1
ii libgpgme11 1.14.0-1+b2
ii libseccomp2 2.5.1-1
ii runc 1.0.0~rc93+ds1-3
Versions of packages podman recommends:
ii buildah 1.20.0+ds1-1
ii fuse-overlayfs 1.4.0-1
ii golang-github-containernetworking-plugin-dnsname 1.1.1+ds1-4+b4
ii slirp4netns 1.0.1-2
ii tini 0.19.0-1
ii uidmap 1:4.8.1-1
Versions of packages podman suggests:
ii containers-storage 1.24.8+dfsg1-1+b1
ii docker-compose 1.25.0-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libpod
Source-Version: 3.0.1+dfsg1-2
Done: Reinhard Tartler <siret...@tauware.de>
We believe that the bug you reported is fixed in the latest version of
libpod, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 987...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Reinhard Tartler <siret...@tauware.de> (supplier of updated libpod package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Wed, 21 Apr 2021 17:36:07 -0400
Source: libpod
Architecture: source
Version: 3.0.1+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team
<pkg-go-maintain...@lists.alioth.debian.org>
Changed-By: Reinhard Tartler <siret...@tauware.de>
Closes: 985379 987207
Changes:
libpod (3.0.1+dfsg1-2) unstable; urgency=medium
.
* Prefer crun over runc, Closes: #985379
* Add depends in iptables, Closes: #987207
Checksums-Sha1:
3d01152efe34ee7c44ccfbf2940e5d7fcaec057d 4941 libpod_3.0.1+dfsg1-2.dsc
7f79272eb9d390b36fbeb6e6b614a6247261a294 15592
libpod_3.0.1+dfsg1-2.debian.tar.xz
Checksums-Sha256:
d3321bd2428c7d6c58c08f4886a3454cdd4b000778e24cbffbb835447fd52a8f 4941
libpod_3.0.1+dfsg1-2.dsc
1199de701625272f67e10f501d7e80aa3a9330aed73072152fd7cef333689219 15592
libpod_3.0.1+dfsg1-2.debian.tar.xz
Files:
9e36832ee01dce39b05d029fc2206433 4941 admin optional libpod_3.0.1+dfsg1-2.dsc
65f77e5e3f54a757ceb0b5b24813a417 15592 admin optional
libpod_3.0.1+dfsg1-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmCAn2MUHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJstRqA/+KbhKKU+dST62cRnTv4HSEvWbHDk2
y2ESs5HdTFxcURzw8U2dvAxnGk9u/ypvyYGIj3ZlmaS9KEAJ9PYQnB8qGbG/19lm
VXG0fkrRhjDjqKyUuWES8xRyTBcfWsc30pVg67TdnzkJCQ8J5qWUkWI5iGFZR7/b
P8W1+Y7EnVq04HTS8dT9FF/7UY0pdxRFhPFe9TEPHT4mdKggS6jLOpE9qvWCqp3a
bw6eLJgwFg2W/SqTjMcxhqmzy7JsEzlL9zU4BFx0fB6Po0uNbTpyjP8Hg9v7u5kQ
Fp42LMcbo07d+nWmtxxd9JJ/KObJDo8rwB/krIMcOenPES/R3adqvnbGF8AaZJVQ
CUMf0XD0uVmXQhh7gvX++zueHkuWuXY9ePZYoPQKrX9/PMBkIlb0BvPH5qwXHLXe
hltCQvpsJ+KZvkPv7mTgDCaPOgPKj2l0fIjfa56NFAXARfKYtNWFzrhj0w+lbNol
lQpdcBwYtgXxKTPOZalhOUrcRPagFYCbqio1ZgSIy/aY9E/IBjWwyWb7dkgVWodt
EtTtdj2dHyIVm7rqrYdagIr6FgFGCUjNEARgWUllWCBYM6MZy5Zm/WAFv2I3i4Mn
QgXKe8+biFXXWA6RuaBOOg2Xi2XHBJJ2uk8n1Uvj8NhgTCvMm6ifH11Z/rypEBY9
eUFnKhH++wKVwnA=
=jl47
-----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
