Cannot fetch docker.io/savonet/liquidsoap:latest

[amunrarara]

Description

Directly fetching any tagged version, such as docker.io/savonet/liquidsoap:7d2ffd5, works fine. But fetching the latest image returns the following error:

 => ERROR [liquidsoap internal] load metadata for docker.io/savonet/liquidsoap:latest                                                                                                                    0.3s
------
 > [liquidsoap internal] load metadata for docker.io/savonet/liquidsoap:latest:
------
failed to solve: savonet/liquidsoap:latest: failed to resolve source metadata for docker.io/savonet/liquidsoap:latest: docker.io/savonet/liquidsoap:latest: not found

I can pull other images A OK, but this one's not available.

Steps to reproduce

1. docker pull savonet/liquidsoap
2. Feel the sadness

Expected behavior

1. docker pull savonet/liquidsoap
2. Receive the image successfully

Log extracts

No response

Script extracts

No response

Liquidsoap version

n/a

Liquidsoap build config

n/a

Installation method

From official container image

Additional Info

No response

[gAlleb]

Directly fetching any tagged version, such as docker.io/savonet/liquidsoap:7d2ffd5, works fine. But fetching the latest image returns the following error:
docker pull savonet/liquidsoap
Feel the sadness

Nothing to be sad about.
Latest is a tag like any other tag, and if it exists, it's because someone explicitly pushed an image with that tag.

if you omit the tag entirely and pull using just savonet/liquidsoap, Docker defaults to using latest - it is how Docker works. So, in this case, docker pull savonet/liquidsoap is equivalent to docker pull savonet/liquidsoap:latest which results to nothing, again, because latest is a tag like any other tag and should be explicitly pushed by a dev.

And of course, if a dev sees no reason to make a latest tag releases - it is absolutely ok. If you want super latest - there is savonet/liquidsoap-ci-build:TAG where almost every commit is pushed to.

[toots]

I'll try to add latest in the release workflow.

By nature of our development, it's not clear what latest should be.

We really want users to know which version they install as this has a lot of implications.

[amunrarara]

Thanks for your apt description @gAlleb and @toots . I use Docker quite a lot in professional and personal projects, this isn't new to me, but it isn't well-stated in your documentation. Maybe update the DockerHub description page to state that? It isn't clear that this would be the case. The Liquidsoap docs don't state anything of that nature, either.

[amunrarara]

I see "Installed packages are those generated during our CI process, not the official debian package! Images are tagged by the branch that was used to generate them". Perhaps that's what's meant to communicate what you shared above? Unfortunately that does not communicate very clearly, to me at least, if that is the case.

[toots]

Thanks for the feedback. I added a docker pull example in 1dfbe88.

I was looking for a similar situation and, for instance, if you look at the debian docker images, they also do not have a latest tag, for the same reason: https://hub.docker.com/_/debian/tags

[amunrarara]

Ok awesome, glad it was good feedback.

Liquidsoap is rockin' awesome, by the way. I'm running a lil' synthwave radio station to Nostr (Zap.Stream) if y'all are interested in the genre:

https://zap.stream/naddr1qq9rzde5xvcryvee8ycsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qgsqtespt8c7pfktvna9w07pa034lxz6jaw7le7h2cplmw0gelfcxdqrqsqqqan807q027