[pkg-go] Bug#970352: unprivileged podman dies with gibberish

[Reinhard Tartler]

Control: close -1
Control: tag -1 unreproducible

Hi Harald,


On Sun, Sep 20, 2020 at 11:32 AM Reinhard Tartler <siretart at gmail.com>
wrote:

> Control: tag -1 upstream
>
> On Sun, Sep 20, 2020 at 9:28 AM Harald Dunkel <harri at afaics.de> wrote:
>
>> I think there is a misunderstanding: The problem is not the error,
>> but the error *message*. Can you do without complaining about bad
>> HTTP code and URLs that don't work? Surely they don't give a hint
>> about what is wrong. They are just distracting.
>>
>>
> That was not clear to me from the initial description. In any case, I
> think the most efficient way to resolve this is to ask upstream. May I ask
> you to file an upstream report at
> https://github.com/containers/podman/issues/new ? I could do so on your
> behalf, but it'd be more efficient if you could do so yourself.
>
> Let me know how you prefer to proceed.
>
>
I've read the 'gibberish' again, and have to ask for clarification. It
seems to be this report is actually about two

The "gibberish" is not what is causing podman to "die". The relevant part
of the output probably is this:

ApplyLayer exit status 1 stdout:  stderr: there might not be enough
IDs available in the namespace (requested 0:42 for /etc/gshadow):
lchown /etc/gshadow: invalid argument

I would have hoped that the instruction in README.Debian would have
helped, but you indicated that you are using a custom, non-Debian
kernel, so there is no way for me to reproduce this crash. I have to
ask you to try again with a Debian kernel and report this issue to
upstream.

The other issue in your report happens when you instruct podman to
fetch an image without fully qualifying what registry to get the image
from. In this case, podman will search several registries as
configured in /etc/containers/registries.conf. The Debian package
configures "quay.io" and "docker.io" in that order. The image you
specified is not available on quay.io, but on docker.io, and this
causes some warnings that might be considered confusing. I'm not sure
what kind of formatting or behavior would be more helpful to both
users and developers that have to triage user errors.

As package maintainer, I don't think I can support you well with
either of these issues. I'd strongly encourage you to discuss both
upstream at https://github.com/containers/podman/issues/new. Let me
know the bug numbers, I'm happy to repoen this report with appropriate
linking to the upstream bug.


-- 
regards,
    Reinhard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-go-maintainers/attachments/20200926/46c1d3bc/attachment.html>