From: divoplade <d@divoplade.fr>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>,
"Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: Gitlab CI
Date: Sat, 25 Jul 2020 00:28:19 +0200 [thread overview]
Message-ID: <017f3a1f7a42e28b6784c1945b5765704ed5a07e.camel@divoplade.fr> (raw)
In-Reply-To: <87pn8l6l4g.fsf@gnu.org>
Hello,
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.
Moreover, running this command as part of a CI job just to push it to
docker hub will require a privileged container. So you will need to
either provide your own runner, or provide you own docker registry
(docker hub or else).
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.
divoplade
next prev parent reply other threads:[~2020-07-24 22:28 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 [this message]
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=017f3a1f7a42e28b6784c1945b5765704ed5a07e.camel@divoplade.fr \
--to=d@divoplade.fr \
--cc=help-guix@gnu.org \
--cc=jeremy@korwin-zmijowski.fr \
--cc=ludovic.courtes@inria.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).