[Bug]k3d start doesn't bring back the server container about k3d HOT 8 CLOSED

Cool, thanks for the update :)
I'll close the issue then 👍

from k3d.

Just released v1.2.0, you may want to try it with this one 👍
Easy installation via: wget -q -O - https://raw.githubusercontent.com/rancher/k3d/master/install.sh | bash

from k3d.

Hey, thanks for opening this bug report. I guess this is a similar issue to #54. Can you reproduce this with the latest dev build or with a custom build from the top of the master branch?
Which version do you use at the moment?
I will create a new non-dev release soon.
A workaround would be to use the --all option to start it via k3d (along with all other stopped clusters)

from k3d.

Thank you for getting back this fast. Just installed k3d version v1.1.0. Let me try this and see if I get the same results. By the way this is a great project keep it up. I am just getting started with k8s and with my machine being so low on specs minikube works but k3s is actually what I have been looking for.

from k3d.

Thanks, it actually starts if you add --all otherwise it behaves the same way.

from k3d.

I just checked with the master branch and this works fine when I use Docker for Desktop on windows

from k3d.

Hi @rugwirobaker , I couldn't reproduce this with v1.2.0... can you please give some more details?

• Which version of k3d are you currently using?
• Which OS are you on?
• Which commands did you issue to hit this problem?
• Can you check the logs of the server container with docker logs please?

from k3d.

Hello @iwilltry42,
my bad, just went back and retraced my steps, first by stopping the cluster with k3d stop --name <custom-name> on restart the server cluster is up and running, then I powered off my laptop without stopping the container and on reboot restarted the cluster with k3d start --name <custom-name> which also worked. I can confirm that the bug was solved as far as I am concerned.

My setup:

• k3d version v1.2.0
• ubuntu 18.64, amd64

from k3d.