This message was deleted.
# k3s
a
This message was deleted.
s
Yes, K3S servers will run workloads, essential if you have a single server K3S cluster. Yes, you can create all three of your nodes as server nodes and you can end up with an HA cluster.
a
Brilliant. Thanks for your help Mark
I don't suppose you know why the command documented to install docker from rancher fails with the error 'redirection unexpected'? https://docs.k3s.io/advanced curl https://releases.rancher.com/install-docker/24.0.sh | sh
s
Sorry, no. I've never needed to do that. I've been fine with the built-in containerd.
f
I don't know why and don't work here anymore to fix it but none of the 24.x are published to the CDN.. you can just get it from here: https://github.com/rancher/install-docker/tree/master/dist , or if you want the latest version anyway straight from Docker (the main point of these is to be able to get older ones since Docker only easily provides the latest)
a
Thanks. It worked from the raw github site
now, even though I have disabled the firewalls and ufw, i am unable to follow this guide to uninstall multiple server nodes: https://docs.k3s.io/datastore/ha-embedded The first node looks to come up, but additional ones fail to start. Then looking at the primary node the service is restarting and reporting this error: level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://127.0.0.1:6443/v1-k3s/readyz: 500 Internal Server I have put the full IP address in of the primary on the secondary nodes. All I am doing different is adding the --docker parameter to use docker as the runtime. My primary node was already running some docker services so I wanted to keep that.
a
Any reason u stick with docker, as k3s default with containerd ?
a
Yes, I am using an existing package called Stereum that manages some eth node services on the node, but it uses Docker already