"docker pull" in container registry is hard-coded...

[mteufel]

Feature Description

When you are using Gitea Packages as a container registry for each pushed image you can view a page which shows you the command to pull it. I think this is implemented in the file shown in the screenshot. The command "docker" (line 14) seems to be hardcoded there, but there are also users who dont use docker, maybe they use podman... so it would be nice to make this hardcoded text "docker" changeable via configuration.

Screenshots

No response

[silverwind]

In most cases with podman, docker is an alias to podman, but I guess for really pedantic users, we can make this string configurable. Ideally it would be a per-user setting.

[TheFox0x7]

Hi pedantic user here who doesn't have the alias set (which breaks stuff for some apps that rely on docker command) :)

How about not adding docker pull at all? Taking github as an example of a terrible UX for me:
https://github.com/go-gitea/gitea/pkgs/container/gitea

I have to explicitly select the image name, which copies the entire command and then copy the part I'm interested in. I'd argue that for things like compose, quadlets, kubernetes files or UI platforms user is first interested in image name instead of a full pull command.

Plus that's fully platform agnostic out of the box.

Quay is slightly better but that's redhat which also started podman efforts. The digest copy is a nice feature though.

[silverwind]

Or we make a tabbed UI that allows selecting between docker and podman. The problem is not new in itself, for JS package manager there exists a similar situation with npm,pnpm,yarn etc. I guess it would be sufficient to remember the selected tab in localStorage on the client.