[Bug]k3d start doesn't bring back the server container

[rugwirobaker]

Issuing the command: k3d start --name <custom name> after a reboot where in the previous session I didn't stop the cluster only my worker nodes(containers) come up but not the server node.
The output shows that the container was started but it actually is not present.

2019/05/18 15:59:20 Starting cluster [prometheus] 2019/05/18 15:59:20 ...Starting server 2019/05/18 16:00:01 ...Starting 5 workers 2019/05/18 16:00:42 SUCCESS: Started cluster [prometheus]

Here is the docker ps output:

And of course you can't get cluster information since the master is absent:
$ export KUBECONFIG="$(k3d get-kubeconfig --name='prometheus')"
2019/05/18 16:08:45 No server container for cluster prometheus

[iwilltry42]

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)

[rugwirobaker]

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.

[iwilltry42]

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

[rugwirobaker]

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

[zeerorg]

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

[iwilltry42]

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?

[rugwirobaker]

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

[iwilltry42]

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