[Sorry for not answering to Lennart's mail directly - it somehow got lost on
my side so I have to copy/paste it from the archive.]
>> I set up two (hopefully) identical debian containers in nspawn for a single
>> service (DNS) on a debian host. Today's "apt upgrade" now throws
>> permissions
[Sorry for not answering to Lennart's answer directly - it somehow got lost so
I have to copy/paste it from the archive.]
>> I set up two (hopefully) identical debian containers in nspawn for a single
>> service (DNS) on a debian host. Today's "apt upgrade" now throws
>> permissions problem on
Hi ML,
currently I am seeing differences between two, what I consider identical,
nspawn-containers which prevents me to update one of them. (Lots of) details
are at the end of the mail.
I set up two (hopefully) identical debian containers in nspawn for a single
service (DNS) on a debian
Dear Lennart & list,
thank you for taking your time to answer (and for systemd :-) )!
(TL;DR -> SOLVED)
On Mittwoch, 19. April 2017 18:37:58 CEST Lennart Poettering wrote:
> > == On the host:
> > $ groupadd -g3777036288 MY_GROUP
>
> Don't do this. If you register the group like this, nspawn
Hi!
On the bug tracker guideline page it said that the systemd-devel-list
is also meant for support, so I hope it's okay to ask here this beginnger's
question:
== Environment:
- systemd-232 (systemd-232-22_amd64)
- Debian Stretch (minbase + systemd + systemd-container + ...)
==
Hi!
On the bug tracker guideline page it said that the systemd-devel-list
is also meant for support, so I hope it's okay to ask here this beginnger's
question:
== Environment:
- systemd-232 (systemd-232-22_amd64)
- Debian Stretch (minbase + systemd + systemd-container + ...)
==
