Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add 1.X-debian-stable type alias #485

Closed
Jorropo opened this issue Aug 18, 2023 · 3 comments
Closed

Add 1.X-debian-stable type alias #485

Jorropo opened this issue Aug 18, 2023 · 3 comments

Comments

@Jorropo
Copy link

Jorropo commented Aug 18, 2023

Hey I am maintaining some software and I recently noticed that some of our docker images were built with the wrong version of go (1.19.10 when 1.19.12 was the latest on the 1.19 branch at the time).
AFAIT this is because buster was no longer supported and you switched to bullseye and bookworm instead.
So I should have used 1.19-bulleyes or 1.19-bookworm images, however our docker deployment is automated and we only really look at it when bumping the major go version (we don't do that automatically due to regressions in the go std ipfs/kubo#10065)

As a maintainer that rely on your work it would make my life easier if you could provide an alias along the lines of 1.X-debian-stable where X is 20 or 21 to take the current releases of go as example. Exactly like you already do for -alpine.

I guess for consistency the full matrix of precision should also be supported like you do for alpine so:

  • 1.X.Z-debian-stable
  • 1.X-debian-stable
  • 1-debian-stable
  • debian-stable

But I personally don't need it.


I'm not sure about -debian-stable, -debian or something else could very well be a better name.

Thx 🙂

Jorropo added a commit to Jorropo/golang that referenced this issue Aug 18, 2023
Based on:
debuerreotype/docker-debian-artifacts#205 (comment)
I have based the `*debian-stable` not on an alias but on a different debian channel.

Fixes docker-library#485
@yosifkit
Copy link
Member

Debian is the default variant and the current stable (bookworm) is the default release. So we already have 1.21.0, 1.21, 1, latest and 1.20.7, 1.20 tag sets to choose the newest stable Debian with go 1.21 (or 1 or 1.20).

@Jorropo
Copy link
Author

Jorropo commented Aug 18, 2023

I see, I missed the Shared Tags section.

Technically debian stable and bookworm are different (stable use a different sources.list which implicitly rolls to the next debian stable release) but I don't need it in my case.

Thx

@Jorropo Jorropo closed this as not planned Won't fix, can't repro, duplicate, stale Aug 18, 2023
@tianon
Copy link
Member

tianon commented Dec 12, 2023

I like to use the analogy of a "square wheel" in relation to the way debian:stable "rolls" 😄 (a vehicle with square wheels is not going to be a smooth ride 🙈)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants