This message was deleted.

Thanks @wide-garage-9465! I attempted to upgrade, but has found two issues so far: 1. Some state seems to be persistent that prevents me from creating a named cluster even if

k3d cluster list

shows no clusters, and no k3d/k3s containers running. 2. DNS issues. Seems like I cannot reach hosts external to the cluster anymore. I assume others have reported issues, since https://github.com/k3d-io/k3d/releases/tag/v5.7.1 was created already.

Hey @broad-laptop-19151! #2 is a regression - I reverted the related changes and released v5.7.1 (see https://github.com/k3d-io/k3d/issues/1462) #1 is new - do you have more details/logs? Did you remove the existing clusters with

k3d cluster delete

?

I am AFK now, but will try to report more details when I am back. The k3d CLI reported no clusters (k3d cluster list) and I ran «k3d cluster delete —all» multiple times. And no containers (docker ps). Still «k3d cluster create name» was complaining about existing cluster. If I changed the cluster name it started. Any idea where that state is persisted?

It's looking for any containers, started or stopped. Also volumes or networks may conflict.

Ah, thanks. It might be network then. I did a docker cleanup, and noticed an obsolete network. Thanks!