From: Simon Josefsson via <help-guix@gnu.org>
To: help-guix@gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>,
suhail@bayesians.ca, "Cayetano Santos" <csantosb@inventati.org>
Subject: Container image entrypoints on Gitlab (was: Re: Building a Docker image for GitLab-CI)
Date: Mon, 23 Dec 2024 19:08:45 +0100 [thread overview]
Message-ID: <87frmes24y.fsf_-_@kaka.sjd.se> (raw)
In-Reply-To: <87ldw7pp6d.fsf@kaka.sjd.se> (Simon Josefsson via's message of "Sun, 22 Dec 2024 19:07:06 +0100")
[-- Attachment #1: Type: text/plain, Size: 2722 bytes --]
Simon Josefsson via <help-guix@gnu.org> writes:
> I didn't test now but I think Debian images handle all three entrypoint
> values, but the 'guix pack' image doesn't.
That was not true! Here the situation:
https://gitlab.com/debdistutils/guix/container/-/pipelines/1600726433
Debian fails on these two GitLab .gitlab-ci.yml variants:
image:
name: debian:stable
entrypoint: ["/bin/sh"]
image:
name: debian:stable
entrypoint: ["/bin/sh", "-c"]
And works on these two variants:
image:
name: debian:stable
entrypoint: [""]
image: debian:stable
The last one is what I suppose most people want to use. One shouldn't
have to specify entrypoint's when using GitLab CI/CD images.
My Guix container:latest works on these three variants:
image:
name: debian:stable
entrypoint: ["/bin/sh", "-c"]
image:
name: debian:stable
entrypoint: [""]
image: debian:stable
And fail on this variant:
image:
name: debian:stable
entrypoint: ["/bin/sh"]
At least we are not worse than Debian here.
However there is another difference, local run of Debian images handle
both these variants:
jas@kaka:~/src/guix-container$ podman run -it --rm debian:trixie-slim
root@f9634c8d6b63:/#
exit
jas@kaka:~/src/guix-container$ podman run --entrypoint /bin/sh -it --rm debian:trixie-slim
#
jas@kaka:~/src/guix-container$
But my Guix images doesn't:
jas@kaka:~/src/guix-container$ podman run -it --rm registry.gitlab.com/debdistutils/guix/container:latest
Error: no command or entrypoint provided, and no CMD or ENTRYPOINT from image
jas@kaka:~/src/guix-container$ podman run --entrypoint /bin/sh -it --rm registry.gitlab.com/debdistutils/guix/container:latest
sh-5.1# exit
jas@kaka:~/src/guix-container$
Presumably because of a missing '--entry-point=/bin/sh' when building
the images using 'guix pack'. So let's add it! Yes this now works:
jas@kaka:~/src/guix-container$ podman run -it --rm registry.gitlab.com/debdistutils/guix/container:latest2
sh-5.1# exit
jas@kaka:~/src/guix-container$ podman run --entrypoint /bin/sh -it --rm registry.gitlab.com/debdistutils/guix/container:latest2
sh-5.1# exit
jas@kaka:~/src/guix-container$
However this breaks GitLab CI/CD usage:
image: $CI_REGISTRY_IMAGE:latest2
https://gitlab.com/debdistutils/guix/container/-/jobs/8713593164
Ouch, that is the primary use-case we want to support!
So until someone figures this one out, I've opted that the default
images require --entrypoint when invoked local on laptops with podman
but work without any configuration from GitLab shared runners and normal
.gitlab-ci.yml usage.
/Simon
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next prev parent reply other threads:[~2024-12-23 18:09 UTC|newest]
Thread overview: 17+ 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
2024-12-18 19:17 ` Simon Josefsson via
2024-12-18 22:31 ` Cayetano Santos via
2024-12-17 7:52 ` Ludovic Courtès
2024-12-17 8:07 ` Simon Josefsson via
2024-12-17 10:24 ` Ludovic Courtès
2024-12-17 23:46 ` Simon Josefsson via
2024-12-21 15:33 ` Ludovic Courtès
2024-12-22 18:07 ` Simon Josefsson via
2024-12-23 18:08 ` Simon Josefsson via [this message]
2024-12-25 18:13 ` Container image entrypoints on Gitlab Simon Josefsson via
2024-12-23 18:57 ` GitLab container /etc symlink problem (was: Re: Building a Docker image for GitLab-CI) Simon Josefsson via
2024-12-25 20:38 ` Building a Docker image for GitLab-CI Simon Josefsson via
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=87frmes24y.fsf_-_@kaka.sjd.se \
--to=help-guix@gnu.org \
--cc=csantosb@inventati.org \
--cc=ludo@gnu.org \
--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.
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).