From: Andreas Enge <andreas@enge.fr>
To: Simon Josefsson <simon@josefsson.org>
Cc: help-guix@gnu.org, ludovic.courtes@inria.fr, suhail@bayesians.ca,
Cayetano Santos <csantosb@inventati.org>
Subject: Re: Building a Docker image for GitLab-CI
Date: Mon, 16 Dec 2024 12:04:37 +0100 [thread overview]
Message-ID: <Z2AJRccAAH9bIflo@jurong> (raw)
In-Reply-To: <87ed27oqn9.fsf@kaka.sjd.se>
Hello Simon,
Am Mon, Dec 16, 2024 at 11:42:34AM +0100 schrieb Simon Josefsson via:
> I am trying to get a Guix container usable in GitLab, and thought I'd
> share my status. I have established working networking in the resulting
> Guix container, which seems like progress (whoohoo!). tl;dr:
at work we are using gitlab CI to build guix docker containers and run a
node on openshift for the bordeaux build farm:
https://gitlab.inria.fr/enge/plm-guix
The README.md is completely outdated and serves mainly as a reminder to
myself on how this docker thing works; every time I look at it after a
break of a few months I have forgotten how to use a docker container...
And of course I have already forgotten the details; probably we should
write a little blog post. I will talk about it with my colleague when I
meet him next year ;-)
We also start with a Debian image and use a Dockerfile to install Guix
in it, as described in the Guix manual. Then for CI, we use this fixed
docker image to create a new one every time our repository (with a
channels.scm file and the plmshift.scm OS configuration file) changes.
In our case, this second docker image is the artefact that we then deploy.
We use "docker in docker" to create the images, and if I understood
correctly, this requires some privileges; these may not be given on
gitlab.com, but are available in our self-hosted instance.
Andreas
next prev parent reply other threads:[~2024-12-16 11:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 12:36 Building a Docker image for GitLab-CI Suhail
2024-12-15 21:05 ` Cayetano Santos
2024-12-15 21:27 ` Cayetano Santos
2024-12-16 10:42 ` Simon Josefsson via
2024-12-16 11:04 ` Andreas Enge [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-13 10:31 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
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z2AJRccAAH9bIflo@jurong \
--to=andreas@enge.fr \
--cc=csantosb@inventati.org \
--cc=help-guix@gnu.org \
--cc=ludovic.courtes@inria.fr \
--cc=simon@josefsson.org \
--cc=suhail@bayesians.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.