Hello -
I too have found that debugging is a challenge when a service's
stdout/stderr aren't captured automatically. From my point of view though,
the issue is not just that certain binaries lack syslog support: since a
service implementation's gexp can do much more than just exec a binary, and
si
I've observed this error under similar circumstances: launching a guix
system container script with network sharing enabled, on a foreign disto
(Debian 10) with nscd running.
Using `strace -f /gnu/store/...-run-container`, we can observe the
container's lookup of user accounts via the foreign dist
An older bug (https://issues.guix.info/issue/37662) discusses a similar
issue, but for a foreign distro with Guix installed (not a native Guix
distribution).
That bug mentions two things:
- make sure that either ‘glibc-utf8-locales’ or ‘glibc-locales’ is
installed (as root)
- make sure that the G
up.html
On Mon, Aug 24, 2020 at 11:15 PM conjaroy wrote:
> I've observed this error under similar circumstances: launching a guix
> system container script with network sharing enabled, on a foreign disto
> (Debian 10) with nscd running.
>
> Using `strace -f /gnu/store/...
My pleasure, Edouard. Thanks for the doc update!
Jason
On Sun, Sep 13, 2020 at 6:39 AM wrote:
> Thank you for this thourough investigation and for finding the
> workaround !
>
> I just submitted a patch to the doc based on your email.
>
> Cheers,
>
> Edouard.
> c
Hello Ludo',
A separate nscd per container also seems like a reasonable option. However,
for the sake of machines hosting many long-lived containers, perhaps we
should consider reducing the cache size: currently it's 32MB for each name
service type, with an expiration of 12-24 hours:
https://git.
Sure, I'm happy to take a stab at this.
Jason
On Mon, Sep 14, 2020 at 3:28 AM Ludovic Courtès wrote:
> In that case, we can have ‘containerized-operating-system’ provide its
> own NSS configuration with a reduced cache size (or without cache since
> there’s caching happening on the host for hos
