-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Debian Jessie has end of security support in May 2018 #264
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
Comments
$ bashbrew list --uniq python | grep stretch
python:3.7.0b1-stretch
python:3.7.0b1-slim-stretch
python:3.6.4-stretch
python:3.6.4-slim-stretch
python:2.7.14-stretch
python:2.7.14-slim-stretch Full list of all stretch-related aliases of the above unique tags: $ bashbrew list python | grep stretch
python:3.7.0b1-stretch
python:3.7-rc-stretch
python:rc-stretch
python:3.7.0b1-slim-stretch
python:3.7-rc-slim-stretch
python:rc-slim-stretch
python:3.6.4-stretch
python:3.6-stretch
python:3-stretch
python:stretch
python:3.6.4-slim-stretch
python:3.6-slim-stretch
python:3-slim-stretch
python:slim-stretch
python:2.7.14-stretch
python:2.7-stretch
python:2-stretch
python:2.7.14-slim-stretch
python:2.7-slim-stretch
python:2-slim-stretch |
Will the default be stretch? |
At some point, yes; transition timeline TBD (especially since it's a bit of
a breaking change for a lot of folks).
|
Please include a |
Actually that is not really true. All Debian stable releases are LTS (Long Time Support) releases these days. Debian LTS team gives atleast 5 years of support to every Debian stable release including Debian Jessie. When support from the Debian security team ends Debian LTS team will take over the control and they will continue to support the Debian release. E.g the Debian Jessie will be supported by Debian LTS team until atleast mid 2020. Debian 8.0 "Jessie" was released in April 2015, so you can expect that Debian LTS team will support it until atleast April 2020. Similarly Debian 9.0 "Stretch" was released in summer 2017, so you can expect that Debian LTS team will support it until atleast summer 2022. You can read about Debian LTS support here: |
@tianon it looks like the floating tag |
@macropin correct -- for every image update, there'll be a PR here (https://github.com/docker-library/python), followed by a PR to See also "Image updates:" under "Quick reference" on https://hub.docker.com/_/python/. |
I have a related question, it seems like this commit from 7 days ago changed the 3-slim tag to point to the stretch-based version instead of the jessie-based one (even though it's not mentioned in the commit message): docker-library/official-images@f200d7f#diff-051bb6df61b6c6e7f8c1868985011b07 But it's not in the docker hub registry yet. Is there some delay for review? If so, is there any place where I can track the process until the official-images repo is in sync with the images published on hub.docker.org? (At least some of) the other changes in this commit are already live, e.g. "alpine" points to the alpine-3.7 based version instead of the previous alpine-3.4. Or maybe that's a bug in the git repo -> docker hub sync tool and the new 3-slim tag should already be live? |
Thanks @w-flo, it looks like our logic to avoid no-op pushes to the Docker Hub is causing tag swapping to not work. 🤔 We'll try to get it fixed as soon as possible. |
Thanks @yosifkit! |
A proper fix for that issue is going to be a little complicated, so
I've gone and manually pushed the offending tags now. Should be
fixed!
|
Thanks @tianon!
|
I don't know if this should be a separate issue. Can we get stretch 3.5 images? I've cloned this repo, copied 3.5/jessie -> 3.5/stretch and up update.sh Would a PR to do that be appropriate? |
@yosifkit Oh thanks! |
Fixed by #308 👍 |
According to https://en.wikipedia.org/wiki/Debian_version_history#Release_table, Debian Jessie will lose security support May of this year.
Are you planning to upgrade these images? They're all based on Jessie.
The text was updated successfully, but these errors were encountered: