This message was deleted.
# k3sa
adamant-kite-43734
03/04/2023, 4:30 AMThis message was deleted.
a
agreeable-church-10406
03/04/2023, 4:30 AM Copy code
root@hl:/home/hlatimer# k3d cluster create testcluster --api-port 6444 --servers 1 --agents 1 --port "30500-31000:30500-31000@server:0"
INFO[0000] Prep: Network
INFO[0000] Created network 'k3d-testcluster'
INFO[0000] Created image volume k3d-testcluster-images
INFO[0000] Starting new tools node...
INFO[0000] Starting Node 'k3d-testcluster-tools'
INFO[0001] Creating node 'k3d-testcluster-server-0'
INFO[0001] Creating node 'k3d-testcluster-agent-0'
INFO[0001] Creating LoadBalancer 'k3d-testcluster-serverlb'
INFO[0001] Using the k3d-tools node to gather environment information
INFO[0001] HostIP: using network gateway 172.19.0.1 address
INFO[0001] Starting cluster 'testcluster'
INFO[0001] Starting servers...
INFO[0001] Starting Node 'k3d-testcluster-server-0'
INFO[0007] Starting agents...
INFO[0007] Starting Node 'k3d-testcluster-agent-0'
INFO[0011] Starting helpers...
INFO[0011] Starting Node 'k3d-testcluster-serverlb'
ERRO[0063] Failed Cluster Start: Failed to add one or more helper nodes: runtime failed to start node 'k3d-testcluster-serverlb': docker failed to start container for node 'k3d-testcluster-serverlb': Error response from daemon: driver failed programming external connectivity on endpoint k3d-testcluster-serverlb (f8cca626bf572dd2b8877deab4116409c1c4268c9bc477b0c09c8117af8b19fd): Error starting userland proxy: listen tcp4 0.0.0.0:6444: bind: address already in useagreeable-church-10406
03/04/2023, 4:30 AManyone seen this issue before?
agreeable-church-10406
03/04/2023, 4:37 AMwelp, got it working after I ran
k3s-killall.shc
creamy-pencil-82913
03/04/2023, 4:59 AMGenerally you wouldn't use k3d on the same host as you've installed k3s as a service. Especially if you want the k3d cluster to use the ports that k3s is already using.
creamy-pencil-82913
03/04/2023, 5:00 AMYou should decide if you want to run k3s as a service or in k3d.
a
agreeable-church-10406
03/04/2023, 3:18 PMoh interesting distinction. I guess I wanted to run k3s as a service but kept running into trouble with the metrics server starting up on port 10250 and the k3s service would just die after a few minutes. I went the k3d just to get something going
n
nutritious-tomato-14686
03/09/2023, 12:01 AMOn ubuntu you may be running into conflicts with ufw firewall. See https://docs.k3s.io/installation/requirements#inbound-rules-for-k3s-server-nodes and https://docs.k3s.io/advanced#ubuntu
39 Views