-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
RHEL 7.6: cluster creation fails for Kubernetes < 1.14 #820
Comments
/assign FWIW on a linux box (~debian testing):
|
this looks like kubernetes/kubernetes#43856 (from the logs you uploaded), I'm not sure what changed in 1.14+ yet though. |
same result on RHEL 7.7 |
@Hendrik-H have you tried using a newer version of docker? |
no, I can only test with the version that I get with RHEL |
Kubernetes 1.13 is out of support upstream now, and I'm pretty sure this docker version isn't supported upstream either. I don't have RHEL, but hopefully the next RHEL release will ship something newer or we'll figure out podman.. Given that upstream supported Kubernetes versions work, I don't think we're likely to pursue this versus other work. |
What happened:
I'm trying to create clusters using kind
0.5.1
and different node images, using the list from https://github.com/kubernetes-sigs/kind/releases/tag/v0.5.0, as there is none for0.5.1
. This works fine forkindest/node:v1.15.3@sha256:27e388752544890482a86b90d8ac50fcfa63a2e8656a96ec5337b902ec8e5157
andkindest/node:v1.14.6@sha256:464a43f5cf6ad442f100b0ca881a3acae37af069d5f96849c1d06ced2870888d
but fails for the other images.The output of the command line is:
What you expected to happen:
That the clusters get created cleanly.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
The logs for a failed cluster creation:
kind-13.zip
Environment:
kind version
):v0.5.1
kubectl version
):v1.15.3
docker info
):17.05.0-ce
/etc/os-release
):RHEL 7.6
The text was updated successfully, but these errors were encountered: