This message was deleted.

Hey 👋 Restart = k3d stop/start or docker/host restart?

Either.

For the latter, it is expected. But k3d start should inject the host-aliases again 🤔 are you using the latest version of k3d? I remember that it was a fairly recent update.

Why is it expected for the docker/host restart?

Because the host-alias injection is done by k3d on create/start. However those changes are not persistent due to the container nature. But k3d also doesn't know about the host/docker restarts, as it is only external. For v6.0.0 I planned to create an agent process that takes over those continuous tasks.

What about on container restart? Like, Docker host is online, but I stop and start the container manually instead of going through

k3d

. Should that preserve the alias?

Nope, only k3d actions are known to k3d. When I started k3d, I wanted to make it as independent as possible and as stateless as possible. That's also why all k3d state is stored as labels. But that's planned to change for the next major release.

Hmm, ok. Anyway to make that alias more permanent with the current version of

k3d

?

Nothing except for using k3d cluster start