Your message dated Fri, 8 Dec 2023 19:33:00 +0200
with message-id <zxnttiuxpstib...@tty.gr>
and subject line Re: Bug#1037091: podman run fails because of missing
~/.config/docker/config.json
has caused the Debian Bug report #1037091,
regarding podman run fails because of missing ~/.config/docker/config.json
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.)
--
1037091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: podman
Version: 4.3.1+ds1-8+b1
Severity: important
Dear maintainer,
the current version of podman does not allow me to run any container due
to the following error message:
Error: stat /home/$USER/.config/docker/config.json: no such file or directory
I can trigger this issue with a simple: podman run debian
However, what container I try to run seems not to matter.
The current version in experimental (4.4.0+ds1-1) is also not working on
my machine.
I cannot say which version introduced this issue as I do not use podman
very often. To the best of my knowledge, the last time I used it, it
worked fine and I do not know of any changes I introduced (beside
updates) which could explain this issue.
However, it still seems at least weird to me, that podman requires (not
just reads optionally) a config file which is in Docker's config dir.
I can append further debugging information if requested.
Thanks
Felix Stupp
-- System Information:
Debian Release: 12.0
APT prefers testing
APT policy: (550, 'testing'), (500, 'testing-security'), (500,
'stable-security'), (400, 'stable-updates'), (400, 'stable'), (350,
'oldstable-updates'), (350, 'oldstable'), (110, 'unstable'), (102,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-9-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages podman depends on:
ii conmon 2.1.6+ds1-1
ii crun 1.8.1-1+b1
ii golang-github-containers-common 0.50.1+ds1-4
ii libc6 2.36-9
ii libdevmapper1.02.1 2:1.02.185-2
ii libgpgme11 1.18.0-3+b1
ii libseccomp2 2.5.4-1+b3
ii libsubid4 1:4.13+dfsg1-1+b1
ii runc 1.1.5+ds1-1+b1
Versions of packages podman recommends:
ii buildah 1.28.2+ds1-3+b1
ii dbus-user-session 1.14.6-1
ii fuse-overlayfs 1.10-1
ii slirp4netns 1.2.0-1
ii tini 0.19.0-1
ii uidmap 1:4.13+dfsg1-1+b1
Versions of packages podman suggests:
ii containers-storage 1.43.0+ds1-8
ii docker-compose 1.29.2-3
ii iptables 1.8.9-2
-- Configuration Files:
/etc/cni/net.d/87-podman-bridge.conflist [Errno 13] Permission denied:
'/etc/cni/net.d/87-podman-bridge.conflist'
-- no debconf information
--- End Message ---
--- Begin Message ---
Given we are not able to reproduce, and have not heard back from Felix,
neither as a response to my question on July 14th, nor to Reinhard's on
September 18th, I'm marking this bug as done.
Regards,
Faidon
--- 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
