Hi! Danny Milosavljevic <dan...@scratchpost.org> skribis:
> On Wed, 21 Oct 2020 17:42:36 +0200 > Ludovic Courtès <l...@gnu.org> wrote: > >> zimoun <zimon.touto...@gmail.com> skribis: >> >> > The tool is 'skopeo' and packaged in Guix. >> > >> > However, push to DockerHub requires an account (by Guix project) which >> > requires... probably non-free JS, at least once. >> >> Hmm OK. Users of Docker wouldn’t have to create an account and run the >> non-free JS, so this is probably acceptable. >> >> The next problem is: what would this image contain? ‘guix pack guix’ is >> probably not enough because people expect the daemon to be running. >> Adding ‘--entry-point=bin/guix-daemon’ probably isn’t good either >> because ‘guix-daemon’ never exits, which I think is contrary to what >> users expect. > > It really depends on how people use the images. > > It's totally normal for docker containers to start services they need in > the foreground on container startup, and people then entering that > running container from the outside anyway (!) using docker tools. OK so this: guix pack guix -f docker -S /bin=bin \ --entry-point="bin/guix-daemon --disable-chroot" might work, right? Someone needs to try because the devil is in the details. To me there are still important unknowns regarding an official Docker image (how to build it, how to upload it), so I’m not confident about getting that done in time for 1.2, but progress on that front is welcome anytime! Thanks, Ludo’.
