I’ve been having mixed results with this recently, if youre using a private registry you might want to pull and retag the image to just rancher/server and ‘rancher/agent’ as well as ‘rancher/agent-instance’. See if that gets you going.
From my understanding that should be set in the /var/lib/rancher/etc/agent.conf with the content of export RANCHER_AGENT_INSTANCE_IMAGE=registry.io/rancher/agent
Rancher 1.2 offline install guide triggered me to look at the catalog entries more closely; Would you say the following could work (lets assume I want to add Mesos Rancher hosts):
Create an on-premise local copy of the the community catalog
Modify the infra-templates/mesos docker-compose.yml to point to my private registry images
Add the custom catalog to my Rancher configuration
Add host -> custom -> Run the command on a host machine.
Would Rancher then look at the infra template and get the images from my private registry?
@balzaczyy; I am going to try to upgrade our offline on-premise 1.1.4 Rancher server somewhere in the next few weeks, to make it work I will have to test my hypothesis. So I will let you know.
I actually tried clone and host the private catalog and made it work. One suggestion, the git should be public accessible. Rancher should support token access to private hosted catalog.
@balzaczyy, I tried the method few days ago with no success. Could see in logs, rancher still trying to get to dockerhub for
rancher/net and other images. First was upgrade and that was no fun…then wiped everything with a fresh install only to see it not work as expected.
My steps (for cattle env):
Create a custom catalog (clone from rancher-catalog)
Push images to internal private registry
Create an environment (default could not be edited) template
Add host (same box where agent would run)
Run agent script on same host
Infra services would not start…times out.
Logs show rancher trying to grab images for infra services from dockerhub…that obviously did not work.