Skip to content

Add images based on Debian 11 (Bullseye) #633

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

Merged
merged 3 commits into from
Aug 16, 2021

Conversation

michael-k
Copy link
Contributor

The stable release of Debian 11 (Bullseye) is expected on 2021-08-14, see https://lists.debian.org/debian-devel-announce/2021/07/msg00003.html

The base images buildpack-deps:bullseye and debian:bullseye-slim are available on Docker Hub.

@tianon
Copy link
Member

tianon commented Aug 12, 2021

I'm +1 on this after the release is officially released (so hopefully next week, barring any nasty surprises for the release team), but it should also drop all stretch variants (we only maintain two tracks per distro, given the large load of compilation that happens for each variation).

@michael-k
Copy link
Contributor Author

after the release is officially released

That's what I expected :)

drop all stretch variants

Done

Copy link
Member

@tianon tianon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@@ -6,9 +6,9 @@ declare -A aliases=(
[3.9]='3 latest'
)

defaultDebianSuite='buster' # TODO buster
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😂

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This caused me a lot of frustration over the past day, can I get more context on the change than "😂 "? And to anyone who uses the FROM python:3.8 on your dockerfile and you are wondering why you are magically having issues installing nodejs in your build, just change your dockerfile to FROM python:3.8-buster

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The 😂 is specifically because we had buster # TODO buster, which is silly (when it got updated to buster in 2a11f61 we forgot to remove the comment).

The update of the default variant was our standard procedure for these repositories and distribution updates like this, and the reason they provide more specific aliases for folks to continue to pin to buster.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Forgive my frustration, having a bit of a crash course in how these images are managed. I find my first comment a little funny now since this is literally the point of the PR. That being said, it just feels weird that so much of the documentation around setting up the docker environment would be around using generic images like Python:3.8, where at any given time, the OS version can change.

This was my mistake for not pinning the version in the first place, thanks for the clarification!

@tianon tianon merged commit f154e5d into docker-library:master Aug 16, 2021
docker-library-bot added a commit to docker-library-bot/official-images that referenced this pull request Aug 16, 2021
Changes:

- docker-library/python@f154e5d: Add Debian 11 (Bullseye) and drop Debian 9 (Stretch) (docker-library/python#633)
@macobo macobo mentioned this pull request Aug 17, 2021
6 tasks
@michael-k michael-k deleted the debian-bullseye branch August 17, 2021 07:45
@blackdog308

This comment has been minimized.

@michael-k

This comment has been minimized.

@blackdog308
Copy link

I'm guessing it could be these changes

Only if you're using python:latest or any other tag that doesn't mention the OS version (eg. python:3.9 instead of python:3.9-buster or python:3.9-bullseye). But I hope you're not doing that.

Thanks @michael-k

Learnt something new today. Appreciate the help.

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 this pull request may close these issues.

4 participants