This message was deleted.

im a tad confused on what your trying to do here. so you successfully setup a embedded registry... and now your trying to connect to the registry over WAN ?

I had 2 nodes, not connected over LAN, but over Tailscale in this case, and was trying to get the agent to pull images from the server. It worked when I set

--node-ip

to be the same as the Tailscale IP, although after I did that, the pods couldn't communicate with each other, I guess it messed up flannel/CNI? I might just drop trying to get the embedded registry to work over WAN for now, its not critical for what we're trying to do currently.

thats really interesting. why dont you just run 2 embedded registries? one on each node....

its a remote/fully wfh company, its how we connect our pcs (not used by customers/prod) as far as I'm aware, you can't stand up an embedded registry on an agent, it would need to also be a server. I was trying to reduce the need for a customer to need to import the airgap images on each agent, by allowing them to pull from the server embedded registry

AGENT Runtime FlagDefaultDescription`--container-runtime-endpoint` valueN/ADisable embedded containerd and use the CRI socket at the given path; when used with --docker this sets the cri-docker socket path`--pause-image` value"docker.io/rancher/pause:3.1"Customized pause image for containerd or docker sandbox`--private-registry` value"/etc/rancher/k3s/registries.yaml"Private registry configuration file