[pkg-go] Bug#1009776: podman: Packages uidmap and slirp4netns should be full dependencies

[Cal.]

My thinking was more along the lines of "If I'm going to run this as
root, I might as well run docker." And I saw podman rootless mode
kinda equivalent to the docker group when using docker. (But I am a
novice with podman, I pretty much just discovered it.)

If you want some comparisons, on Fedora podman rootless just works (I
don't actually know want dependencies they install, because I use it
to run one-off containers on my laptop -- the servers run docker)

The errors were not that cryptic by themselves but required some
googling to understand what binaries were missing and what packages
provided them. I think adding some instructions on the wiki
(https://wiki.debian.org/Podman) should be enough if dependencies are
to be minimal.

On Sun, 17 Apr 2022 at 15:20, Reinhard Tartler <siretart at gmail.com> wrote:
>
> Control: tag -1 upstream
> Control: severity -1 minor
>
> On Sun, Apr 17, 2022 at 9:09 AM Giuseppe <peppecal+debianbugs at gmail.com> wrote:
>>
>> Package: podman
>> Version: 3.0.1+dfsg1-3+deb11u1
>> Severity: important
>> X-Debbugs-Cc: peppecal+debianbugs at gmail.com
>>
>> Dear Maintainer,
>>
>> I really think packages uidmap and slirp4netns should be full-fledged dependencies for podman.
>>
>> I say this because after installing podman and trying to run some containers in rootless mode I found myself fighting cryptic error messages that were solved by installing those two packages.
>>
>
> My thinking when choosing dependencies was:
>
> - podman has significant performance benefits when running as root
> - the podman package dependencies should be as minimal as possible, in particular on system where podman is running as root.
>
> I do sympathize with the cryptic error message. May I ask you to forward your suggestion on wording directly to upstream at https://github.com/containers/podman/issues ?
>
> Please do let me know the  upstream bug number and your thoughts on this.
>
> Best,
> -rt
>