Errors on rancher agent nodes

Archive Rancher 1.x
1

I see these errors occasionally on the rancher agent nodes: What is the issue I need to fix exactly?

ERRO[3299] Handler for GET /v1.18/images/rancher/agent-instance:v0.6.0/json returned error: No such image: rancher/agent-instance:v0.6.0
ERRO[3299] HTTP Error err=No such image: rancher/agent-instance:v0.6.0 statusCode=404
INFO[3299] GET /v1.18/images/rancher%2Fagent-instance%3Av0.6.0/json
ERRO[3299] Handler for GET /v1.18/images/rancher/agent-instance:v0.6.0/json returned error: No such image: rancher/agent-instance:v0.6.0
ERRO[3299] HTTP Error err=No such image: rancher/agent-instance:v0.6.0 statusCode=404
INFO[3299] POST /v1.18/images/create?tag=v0.6.0&fromImage=rancher%2Fagent-instance

2

@bitsofinfo that’s a strange error. Is there a rancher/agent-instance container running? Can you share the output of a docker ps -a from a host where that is occurring? Are you in an air gap type deployment where you don’t have internet or are you otherwise only using privately hosted docker registry?

3

This is a 5 node cluster in azure (centos7, docker 1.9.1, latest rancher) One manager node and 4 agents.

Note that my setup is working fine, this particular node is one of 4, but in addition to my app, its running a load balancer for my apps’ “service”

ps -a output

418b2b15a179        rancher/agent-instance:v0.6.0                 "/etc/init.d/agent-in"   34 minutes ago      Up 34 minutes            0.0.0.0:8080->8080/tcp                         535ec5a1-d120-49fb-8907-793d937f7bf3
275bc879581a        MYIMAGE  "/entrypoint.sh java "   48 minutes ago      Up 48 minutes            8080/tcp, 8090/tcp, 8443/tcp                   154865b2-2ce2-4fcc-9072-81bf4f65924a
687945de0ca6        rancher/agent-instance:v0.6.0                 "/etc/init.d/agent-in"   About an hour ago   Up 51 minutes            0.0.0.0:500->500/udp, 0.0.0.0:4500->4500/udp   bbac5b5d-88e8-47a6-ace3-119c6c696bcf
a371e954e477        rancher/agent:v0.8.2                          "/run.sh run"            3 hours ago         Up 53 minutes                                                           rancher-agent
9e968753b724        rancher/agent:v0.8.2                          "/run.sh state"          3 hours ago         Exited (0) 3 hours ago                                                  rancher-agent-state
bd94d471fc1f        rancher/agent:v0.8.2                          "/run.sh http://10.21"   3 hours ago         Exited (0) 3 hours ago                                                  sad_mcclintock
4

and yes, I am using a private docker registry up in azure I setup myself. Agent’s docker daemons are started w/ --insecure-registry as appropriate.

5

Just curious: if you run docker create rancher/agent-instance:v0.6.0 do you get an error?

My only guess at this point is that the private registry is somehow behaving inconsistently, but that feels like a week guess.