K3d: [FEATURE] k3d start should start associated k3d-registry

[rpocase]

When using a cluster that was created using k3d create --enable-registry, k3d start --name dev does not start the k3d-registry container.

The k3d start command should (by default) start the k3d-registry if the cluster was created with --enable-registry set. This could be disabled via flag (e.g. --start-registry=false).

[Rested]

Just ran into this same issue. Is there a workaround other than deleting and recreating the cluster?
Edit: :man_facepalming: ah of course just docker start k3d-registry, but i think this feature request is good.

[iwilltry42]

Hi there, thanks for opening this issue.
The fix/feature is in master now, see commit 0b7e118046d881dd98c2d605f9b42531abefd36e

[iwilltry42]

Included in https://github.com/rancher/k3d/releases/tag/v1.6.0 :+1: