<sir123>Hello everybody, me again :) I'm trying to work out why my make check is failing. I have two failures: packages and guix-register. I have the logs but nothing is standing out as obvious. I have added one custom package which I think works.. Any advice?
<davexunit>I want to figure out how to better "market" guix to docker enthusiasts.
<davexunit>I had a bit of a disheartening exchange with one on HN last night.
<davexunit>they didn't care about Guix's ability to deduplicate files system-wide because Linux can deduplicate multiple instances of the same shared library in RAM and file systems like btrfs can do the disk deduplication
<davexunit>so having multiple container images that duplicate tons of stuff isn't a big deal.
<remo_>civodul: the biggest of the bumps was the fact that upon boot from the USB stick image, there was insufficient space on / to support the pre-packaged "desktop" config.
<remo_>When I did "guix system init" using the sample "desktop" config, the build failed a few hours in because /tmp filled up with about 1.3 GiB of stuff during the "mesa" build, which was too much for the root fs.
<davexunit>remo_: looks like you forgot to run the cow-store service
<davexunit>also, the installation shouldn't build anything from source
<remo_>I did run that; the problem was that nix-build seems to fill up /tmp (which is part of /) with temporary build artifacts
<davexunit>I really thought this shouldn't be necessary on our installation images. could've been an oversight on our part, but I'm not sure... waiting on someone with more knowledge.
<remo_>If I want to persist the output of guix system init for later inspection (e.g. to see if maybe it did try to get cached packages first, but fell back to fetching and building the source because of some failure), how would I do that?
<remo_>I will try rebuilding my system later today to see if authorizing the hydra key results in a faster build
<davexunit>you could redirect stdout and stderr to a file
<remo_>Oh, I suppose I could. I'll just do that, then.
<davexunit>you won't be able to see the output unless you tail that file from another tty
<civodul>remo_: could you check what's in /etc/guix/acl?
<remo_>Oh, more feedback: the manual did not mention that the user which comes from the provided "desktop" config file will be locked - i.e., its encrypted password entry in the /etc/shadow file starts out as "!". I had to remove that ! to be able to log in as the user account.
<remo_>Most people installing guix might know how to fix such a basic thing, but it would be worth calling out in the manual (or, if it's possible to somehow address the issue in the config file template, that would also be good)
<civodul>so maybe we should mention it elsewhere too
<remo_>Oh. I didn't see it in the installation steps, so I missed it, too.l
<remo_>I think it should be mentioned there briefly, m aybe with a link