Closed lahabana closed 2 years ago
Seems to be caused by the fact that <1.19 doesn't have: https://github.com/k3s-io/k3s/pull/1785
Therefore the server will never succeed there: https://github.com/rancher/k3d/blob/main/pkg/client/cluster.go#L1028
<1.19 is old but I don't see anywhere in k3d a minimal k3s version. Are we expecting this to work? If not should there be a note in the docs?
Hi @lahabana , thanks for opening this issue! Thanks a lot for the research you did :+1: You're indeed right there. Usually, I test new k3d releases with the latest patch releases of the past three minor versions, which kind of matches the Kubernetes Support Cycle. K8s v1.18 reached EOL quite some time ago and thus wasn't tested. We should definitely add a matrix somewhere in the docs/readme to reflect this :+1:
The change on k3d's end was introduced in v5.0.2, so with v5.0.1 you may get it to work.
What did you do
K3D_LOG_NODE_WAIT_LOGS=server /Users/cmolter/code/k3d/bin/k3d cluster create foo -i rancher/k3s:v1.18.20-k3s1 --trace --timeout 120s
What did you expect to happen
Cluster should have started. Instead getting:
Screenshots or terminal output
Which OS & Architecture
Which version of
k3d
k3d version
main (0c57cf24ca65fecba4dd24624a27364def22fbca) matches v5.2.2
Which version of docker
docker version
anddocker info