Missing arguments for creating cluster with registry

[JohanNicander]

When Creating a cluster using the "Create k3d cluster"-wizard, only deviating from default settings by checking the "Create local registry"-option results in a command like k3d cluster create k3d-cluster-314 --servers 1 --registry-create --kubeconfig-update-default.

Running this results in:

❯ k3d cluster create k3d-cluster-314 --servers 1 --registry-create --kubeconfig-update-default
INFO[0000] Prep: Network                                
INFO[0000] Created network 'k3d-k3d-cluster-314'        
INFO[0000] Created image volume k3d-k3d-cluster-314-images 
INFO[0000] Creating node '--kubeconfig-update-default'  
ERRO[0000] Failed Cluster Preparation: Failed to create registry: failed to create registry node '--kubeconfig-update-default': runtime failed to create node '--kubeconfig-update-default': failed to create container for node '--kubeconfig-update-default': docker failed to create container '--kubeconfig-update-default': Error response from daemon: Invalid container name (--kubeconfig-update-default), only [a-zA-Z0-9][a-zA-Z0-9_.-] are allowed 
ERRO[0000] Failed to create cluster >>> Rolling Back    
INFO[0000] Deleting cluster 'k3d-cluster-314'           
ERRO[0000] failed to get cluster: No nodes found for given cluster 
FATA[0000] Cluster creation FAILED, also FAILED to rollback changes! 

Looking at the instructions for the --registry-create command:

--registry-create NAME[:HOST][:HOSTPORT]     Create a k3d-managed registry and connect it to the cluster (Format: NAME[:HOST][:HOSTPORT]
                                                - Example: `k3d cluster create --registry-create mycluster-registry:0.0.0.0:5432`

From this it is clear that the argument for the registry-create flag is missing and that is what causes the error.