bugs
bugs copied to clipboard
coreos
Torcx Availability Schedule
Issue Report
Feature-request of torcx on coreos
This blog post outlines a schedule in the Timeline section for torcx becoming available. Is it no longer true?
I am using coreos for kubernetes and using /etc/coreos/docker-1.12 approach. However, I recently found a simple docker pull bug for which the bugfix was introduced only in 1.13.
Other than that, I am just concerned my use of docker-1.12 would no longer be honored after July 18, 2018, per that blog post.
I am not sure if this is the right channel to inquire about this. Tried asking via twitter some months back. Any insights or news would be highly appreciated.
Ha, it was not that docker bug impacting me. It was simply these images being private.
I also tried this gist, and it seems to have updated my docker to 17.03. However, not sure if your team recommends this method.
See also this coreos-user thread. We're still adhering to the original plan, though obviously not on the original timeline. We'll update the published schedule once we know more.
That gist will work but is not an official recommendation.
@bgilbert I have been following the script here to run with Docker 17.09 for now.
I have a related question when using this same script. The torcx manifest for a given coreos release is:
https://tectonic-torcx.release.core-os.net/manifests/$COREOS_RELEASE_BOARD/$COREOS_RELEASE_VERSION/torcx_manifest.json
Docker 17.09 shows up in the manifest for 1632.2.1 but not for a recent stable version such as 1911.4.0. My question is if its possible to run with 1911.4.0, yet be able to select Docker 17.09?
@charandas You should be able to edit the script to download 17.09 from a previous OS version and run it on a current version. This may not work in the future if old Docker versions require system libraries that get updated in the OS, but I don't believe there have been any such incompatibilities yet.
Only three Docker versions are built for reach OS version: 1.12 and 17.03 for recommended Kubernetes versions, and the default "current" version which changes with new releases. (The current Docker 18.09 release has segfaults that prevent us from updating to it at the moment.)
That's great. I am not sure why the kubespray project ended up making breaking changes for both docker 1.12 and docker 17.03.
https://github.com/kubernetes-sigs/kubespray/issues/3858
Is Docker 17.03 a recommeded version in context of kubernetes/coreos or just kubernetes?
Upstream kubernetes has a list of validated Docker versions here: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG.md
Up until 1.12, Docker 17.03 was the newest version in the list. With 1.12, they validated versions up to Docker 18.06, which is available as the default in all current Container Linux releases.