Docs(GitLab): add entrypoint for distroless image

[Tsafaras]

Summary

Update the docs for the GitLab integration, to make it clear that an entrypoint has to be specified, when a distroless image is being used.

Test Plan

Without specifying an entrypoint when using a distroless image:

It works if you either specify the entrypoint or if the image used in not a distroless one.

[zanieb]

Hm I thought we removed the custom entrypoint in #7054

[Tsafaras]

This is the image I used:

ghcr.io/astral-sh/uv:python3.8-bookworm

Could this be why? My project is still using that Python version.

But, as you can see from the images I posted, uv's version is latest (0.5.1).
Could also have something to do with GitLab and not with uv.

[Tsafaras]

@zanieb Friendly reminder.
Let me know how you want to move on this.

[samypr100]

@Tsafaras On your first image example you're using the distroless image which is not supported in Gitlab as sh does not exist in it. That's actually one of the reason the non-distroless images were added 😄

We do not have custom entrypoints on any of the non-distroless images. The distroless does and defaults to uv as it's the only binary in that container image.

e.g.

Non-Distroless

~/ $ docker inspect ghcr.io/astral-sh/uv:0.5-python3.8-bookworm | jq  -r '.[0].Config.Entrypoint'
null

Distroless

~/ $ docker inspect ghcr.io/astral-sh/uv:0.5 | jq  -r '.[0].Config.Entrypoint'
[
  "/uv"
]

[Tsafaras]

@samypr100 Thank you for the response, especially for the last snippet!
I tried finding something similar as to what you can see on docker hub (example), but I didn't find it on GH's registry. 🤔
In between tests I never considered I had changed the image.

Should I edit the PR to make this change in the relative docs then?

If you're using a distroless image ... blah blah

[samypr100]

Should I edit the PR to make this change in the relative docs then?

I think it's worth adding a note to the gitlab docs, thanks

[Tsafaras]

@samypr100 @zanieb Turned the correction to a note. Please have a look.