This message was deleted.
# general
This message was deleted.
I confirm editing the share-mnt process in the nodePlan (from did the trick. I unlocked rancher-agent from pulling the agent image.
So there's clearly a bug on the Rancher side.
What I did is: Add the following annotation to rancher server ingress (since I was not able to find an existing unauthentified endpoint that serves the server version):
Copy code
<|>: |
                location /rancher-version {
                    return 200 '${rancher_current_version}';
And then, in my cloud-init, add the following step before starting the rancher-agent:
Copy code
# Pull latest Rancher agent
rancher_current_version=$(curl -sfSL ${rancher_url}/rancher-version)
docker pull "${docker_registry_url}/rancher/rancher-agent:$rancher_current_version"
So, when the Rancher agent connects and checks if the share-mnt image is present, docker says yes and the pull is skipped: