From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: divoplade <d@divoplade.fr>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: Gitlab CI
Date: Mon, 27 Jul 2020 09:46:13 +0200 [thread overview]
Message-ID: <87blk11jui.fsf@inria.fr> (raw)
In-Reply-To: <017f3a1f7a42e28b6784c1945b5765704ed5a07e.camel@divoplade.fr> (divoplade's message of "Sat, 25 Jul 2020 00:28:19 +0200")
Hi,
divoplade <d@divoplade.fr> skribis:
> Le vendredi 24 juillet 2020 à 16:30 +0200, Ludovic Courtès a écrit :
>>
>> So presumably a better option is to use an image created like this:
>>
>> guix pack -f docker -S /bin=bin guix --localstatedir
>>
> As you may know, most gitlab server will not let you use the provided
> docker registry, and so the only option will be to push to docker hub.
Yes. What I had in mind was that you would create that image, upload it
to a registry GitLab-CI can pull from, and then refer to that image in
your ‘.gitlab-ci.yml’.
> I prefer the solution in which the pack is a .tar.gz that is directly
> untarred to /; this way it can be run on a shared unprivileged runner
> and the storage can be achieved in the runner itself, via the gitlab CI
> cache.
Ah yes, I guess that would also work, and it’s in fact less tedious.
That amounts to running https://guix.gnu.org/install.sh every time
though, no?
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-07-27 7:46 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
2020-07-24 22:28 ` divoplade
2020-07-27 7:46 ` Ludovic Courtès [this message]
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=87blk11jui.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=d@divoplade.fr \
--cc=help-guix@gnu.org \
/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).