Hey all, I've been using k3d + docker for a few ye...
# k3d
m
Hey all, I've been using k3d + docker for a few years now, Linux Mint. Since the latest docker / k3s / k3d updates multi node clusters fail to restart due to docker assigning new IP addresses on restart. What I do is a) k3d cluster create test, b) k3d node create main -c test, k3d node create worker -c test. The cluster comes up nicely. Then c) k3d cluster stop / start test. It will fail to come up, the lb node will loop to restart. Note sure I have misconfigured my setup somehow. Any hints appreciated!
I should add if I try stop / start several times, eventually it seems to find an ip assignment that looks ok, the cluster seemingly comes up, but the two nodes will go into notready state for having invalid capacity 0 on image filesystem (host disk has several 100GBs free)
Turns out the issue was a mismatch in the k3s version specified on k3d cluster create. I changed it to match the k3s version shown in the k3d --version command, now everything works again.