unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: Gitlab CI
Date: Fri, 24 Jul 2020 16:30:39 +0200	[thread overview]
Message-ID: <87pn8l6l4g.fsf@gnu.org> (raw)
In-Reply-To: <6aa363c1fac60b165e222ecb0b18bf9b1f019231.camel@korwin-zmijowski.fr> ("Jérémy Korwin-Zmijowski"'s message of "Sat, 20 Jun 2020 10:42:11 +0200")

Hello!

I’m late to the party but I’m interested in this discussion…  :-)

Jérémy Korwin-Zmijowski <jeremy@korwin-zmijowski.fr> skribis:

> I am experimenting with Gitlab CI for a Guile project I am working on.
> It is managed with Hall and I would like to benefit the Guix features.

GitLab CI can run jobs directly in a Docker image:

  https://docs.gitlab.com/ce/ci/docker/using_docker_images.html

So it would be interesting to have any easy way for people to create a
Docker image for this purpose.

Colleagues of mine tried ‘guix system docker-image’ for that but that
turns out to not quite work (IIRC gitlab-runner tries to do ‘docker exec
your build command’, which fails here because those images have shepherd
as their entry point).

So presumably a better option is to use an image created like this:

  guix pack -f docker -S /bin=bin guix --localstatedir

and then, in the image, you first need to spawn guix-daemon, perhaps
with ‘--disable-chroot’ because the image lacks build users.

It would be useful also to set the user under which commands run in the
image, similar to the ‘USER’ directive in Dockerfiles.

Thoughts?

It would be nice to make that as smooth as possible and to add a recipe
in the cookbook!

Ludo’.


  parent reply	other threads:[~2020-07-24 14:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-20  8:42 Gitlab CI Jérémy Korwin-Zmijowski
2020-06-20 13:40 ` Ricardo Wurmus
2020-06-23  8:54   ` Jérémy Korwin-Zmijowski
2020-06-20 15:05 ` divoplade
2020-06-23 10:15   ` Jérémy Korwin-Zmijowski
2020-06-23 15:24     ` Jérémy Korwin-Zmijowski
2020-06-25 12:32 ` zimoun
2020-06-25 14:10   ` Jérémy Korwin-Zmijowski
2020-06-25 21:32 ` divoplade
2020-07-06 12:25   ` Jérémy Korwin-Zmijowski
2020-07-06 16:30     ` Debian package with " divoplade
2020-07-08  9:41     ` Pierre Neidhardt
2020-07-24 14:30 ` Ludovic Courtès [this message]
2020-07-24 22:28   ` divoplade
2020-07-27  7:46     ` Ludovic Courtès
2020-07-27 16:31       ` divoplade
  -- strict thread matches above, loose matches on Subject: below --
2020-07-14 16:12 Stephen Scheck
2020-07-29 15:35 Stephen Scheck

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=87pn8l6l4g.fsf@gnu.org \
    --to=ludovic.courtes@inria.fr \
    --cc=help-guix@gnu.org \
    --cc=jeremy@korwin-zmijowski.fr \
    /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).