From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: Reza Housseini <reza.housseini@gmail.com>, help-guix@gnu.org
Subject: Re: Building a Docker image for GitLab-CI
Date: Wed, 5 Jun 2024 10:55:51 +0200 [thread overview]
Message-ID: <ZmAoF1Edz3OEu_Md@jurong> (raw)
In-Reply-To: <87plsx6j59.fsf@inria.fr>
Hello,
Am Tue, Jun 04, 2024 at 01:29:22PM +0200 schrieb Ludovic Courtès:
> My goal would be to be able to use Guix within the image, so I can have
> GitLab-CI spawn ‘guix build’ commands (or similar).
with a colleague we have set up such a system. He has started from a Debian
image and written a docker script to install Guix "manually", which provides
our base image. Then Gitlab CI creates a new image from a channels file in
the git repository we want to monitor. The command we use is
"guix system image -t docker" and not "guix pack"; I am not really familiar
with the second command, and as far as I understand the first one has the
difference of running the shepherd as the docker command, which in our case
starts the guix-daemon and a guix-build-coordinator-agent.
(One addition: We use the patch in
https://issues.guix.gnu.org/70933
to enable chroot in the container and then run the container in privileged
mode.)
Maybe we should write up a little blog post once everything is settled.
Andreas
next prev parent reply other threads:[~2024-06-05 8:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 10:31 Building a Docker image for GitLab-CI Ludovic Courtès
2024-02-14 14:49 ` Andreas Enge
2024-02-14 17:55 ` Efraim Flashner
2024-02-15 8:25 ` Ludovic Courtès
2024-05-31 9:26 ` Reza Housseini
2024-06-04 11:29 ` Ludovic Courtès
2024-06-05 8:55 ` Andreas Enge [this message]
2024-06-06 9:23 ` Ludovic Courtès
2024-06-07 10:56 ` Andreas Enge
2024-06-06 11:39 ` Reza Housseini
2024-06-06 13:12 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2024-02-14 12:36 Suhail
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZmAoF1Edz3OEu_Md@jurong \
--to=andreas@enge.fr \
--cc=help-guix@gnu.org \
--cc=ludovic.courtes@inria.fr \
--cc=reza.housseini@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).