[pkg-go] Bug#1037091: podman run fails because of missing ~/.config/docker/config.json
Control: tag -1 +moreinfo +unreproducible Hi Felix, thanks for taking the time to write a bug report to Debian. I'm sorry to hear that podman does not work for you as you'd expect. It seems to me that you may have an old, possibly modified installation of podman on your system, and I'd expect you wouldn't see this if you installed podman from Debian in a fresh VM or new laptop. If you were, I'd absolutely love to hear about this. In order to recover your system, can you please try the command podman system reset -f You can read upon it at https://manpages.debian.org/podman-system-reset Please let me know if that fixes the issue or whether you had further thoughts or ideas on this. Best, -rt On Sun, Jun 4, 2023 at 8:57 AM Felix Stupp wrote: > 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 libc62.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 libsubid41:4.13+dfsg1-1+b1 > ii runc 1.1.5+ds1-1+b1 > > Versions of packages podman recommends: > ii buildah1.28.2+ds1-3+b1 > ii dbus-user-session 1.14.6-1 > ii fuse-overlayfs 1.10-1 > ii slirp4netns1.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 iptables1.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 > > -- regards, Reinhard ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#1037091: podman run fails because of missing ~/.config/docker/config.json
On Sun, Jun 04, 2023 at 02:52:56PM +0200, Felix Stupp wrote: > 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. > > [...] > > 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. That is indeed weird. Is there any config (either in your .config, or in /etc) that has been modified in your system? For example, do you perhaps have a registry configured, and one that requires a login? An unqualified "podman run debian" could try to resolve this to your local registry, which in turn may require a login, which implicitly calls "podman login", which in turn attempts to read from a variety of config paths, including $HOME/.docker/config.json. Regards, Faidon ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#1037091: podman run fails because of missing ~/.config/docker/config.json
For others having the same issue, just creating an empty file with "touch ~/.config/docker/config.json" does fix the issue. Podman does not seem to require any configuration in there (at least in my case). However, as someone might assume that Podman wants any content there, they still might be virtually hindered to use podman, so I think severity important is still correct. But feel free to reduce that if you think otherwise. ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
[pkg-go] Bug#1037091: podman run fails because of missing ~/.config/docker/config.json
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 libc62.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 libsubid41:4.13+dfsg1-1+b1 ii runc 1.1.5+ds1-1+b1 Versions of packages podman recommends: ii buildah1.28.2+ds1-3+b1 ii dbus-user-session 1.14.6-1 ii fuse-overlayfs 1.10-1 ii slirp4netns1.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 iptables1.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 ___ Pkg-go-maintainers mailing list Pkg-go-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
