This message was deleted.
# k3da
adamant-kite-43734
08/17/2022, 9:44 PMThis message was deleted.
h
high-morning-12231
08/17/2022, 10:22 PMIf I use k3s-arg, the cluster stalls while creating:
Copy code
k3d cluster create --k3s-arg="--datastore-endpoint=<http://127.0.0.1:2379@server:0>"
INFO[0000] Prep: Network
INFO[0000] Created network 'k3d-k3s-default'
INFO[0000] Created image volume k3d-k3s-default-images
INFO[0000] Starting new tools node...
INFO[0000] Starting Node 'k3d-k3s-default-tools'
INFO[0001] Creating node 'k3d-k3s-default-server-0'
INFO[0001] Creating LoadBalancer 'k3d-k3s-default-serverlb'
INFO[0001] Using the k3d-tools node to gather environment information
INFO[0001] HostIP: using network gateway 172.20.0.1 address
INFO[0001] Starting cluster 'k3s-default'
INFO[0001] Starting servers...
INFO[0001] Starting Node 'k3d-k3s-default-server-0'high-morning-12231
08/17/2022, 10:24 PMwait... Figured it out. 127.0.0.1/localhost doesn't route from inside the environment? It seems to work if I use the external ip of my server instead
w
wide-garage-9465
08/18/2022, 5:16 AMYou can use host.k3d.internal to route to the docker host where the cluster is running on
h
high-morning-12231
08/18/2022, 2:07 PMCool! Thank you
92 Views