Simon et al,
On Mon, Jul 01, 2024 at 10:38:55AM +0100, Simon McVittie wrote:
[..]
> Reproducer (this requires the ability to run podman, but no elevated
> privileges):
>
> $ autopkgtest-build-podman --init=systemd --release=sid
> $ autopkgtest hello -- podman --init localhost/autopkgtest/systemd/debian:sid
>
> I see that either `logger id` exits with status 0 or `adduser` ignores
> a nonzero exit status, so in fact the only reason this fails is that
> autopkgtest is being extra-careful and refusing to continue if its
> create-normal-user script produces output on stderr.
>
> On Sun, 30 Jun 2024 at 17:17:47 -0400, Peter Colberg wrote:
> > The permission error is triggered by logger's --id option:
> >
> > podman exec "$container" strace -f adduser --disabled-login --gecos
> > "Temporary autopkgtest user,,," test
> >
> > [pid 370] execve("/bin/logger", ["logger", "--id=369", "--tag=adduser",
> > "--priority=user.crit", "", "--", "The user `test' already exists."],
> > 0x55efa22252d0 /* 7 vars */) = 0
> >
[..
> It could also be argued that this is a logger (util-linux) bug, because
> logger(1) says "otherwise the socket credentials are not modified and
> the problem is silently ignored", but this bug report indicates that
> the problem is in fact not *silently* ignored.
I have seen this problem with logger in some other context before,
but I cannot remember where. Ideally I'd like to see this fixed in
logger.
Is there a reproducer that does not involve podman or adduser?
I have trouble reproducing the logger --id=... failure with just
unshare as a normal user.
Chris
