k3d doesn't work on M1 mac

[jkotalik]

Probably more of a tracking issue for an issue on k3d, but I currently always get a port conflict issue every time I call rad env init dev.

ERRO[0009] Node k3d-radius-dev-serverlb: Failed executing preStartAction 'WriteFileAction': [WriteFileAction] Writing 160 bytes to /etc/confd/values.yaml (mode -rwxr--r--): Write Loadbalancer Configuration: Failed to copy content to container 'e87599ea9a782223ccbf2853d022b880c98990a5d039f6d02427da664d22b249': Put "http://%2Fvar%2Frun%2Fdocker.sock/v1.41/containers/e87599ea9a782223ccbf2853d022b880c98990a5d039f6d02427da664d22b249/archive?path=%2F": context canceled 
ERRO[0009] Failed Cluster Start: Failed to add one or more helper nodes: runtime failed to start node 'radius-dev-registry': docker failed to start container for node 'radius-dev-registry': Error response from daemon: Ports are not available: listen tcp 0.0.0.0:56936: bind: address already in use 
ERRO[0009] Failed to create cluster >>> Rolling Back    
INFO[0009] Deleting cluster 'radius-dev'                
INFO[0009] Deleting cluster network 'k3d-radius-dev'    
INFO[0009] Deleting 2 attached volumes...               
WARN[0009] Failed to delete volume 'k3d-radius-dev-images' of cluster 'failed to find volume 'k3d-radius-dev-images': Error: No such volume: k3d-radius-dev-images': radius-dev -> Try to delete it manually 
FATA[0009] Cluster creation FAILED, all changes have been rolled back!

[AaronCrawfis]

Weird, they claim to have M1 support: k3d-io/k3d#475

[AaronCrawfis]

Take a look at this: k3d-io/k3d#807

[jkotalik]

Currently on 20.10.8 as my version, I'm going to restart my machine when I get the chance and see if that somehow fixes it.

[jkotalik]

Updated everything, restarted computer, etc and now it's working. Closing.