Skip to content
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.

Config ROS image prefix for install and all rancher/os services #2178

Closed
jambajaar opened this issue Dec 15, 2017 · 3 comments
Closed

Config ROS image prefix for install and all rancher/os services #2178

jambajaar opened this issue Dec 15, 2017 · 3 comments

Comments

@jambajaar
Copy link

We use artifactory for docker.io caching.

A normal docker pull rancher/os can be cached as docker pull dockerhub.mycompanyname.com/docker.io/rancher/os

However, we have no way to inject a prefix into Rancher os for installation or service pulls.

We'd like a global prefix we can add to force ROS to always use our mirror.

@niusmallnan
Copy link
Contributor

@jambajaar
Have you tried to custom your upgrade-sources: http://rancher.com/docs/os/v1.1/en/upgrading/#custom-upgrade-sources

@niusmallnan
Copy link
Contributor

I will support this feature in v1.3.0, users can config a global image prefix:

ros config set rancher.environment.REGISTRY_DOMAIN xxxx.yyy

@kingsd041
Copy link
Contributor

Tested with rancheros-v1.3.0-rc1.
The use of ros config set rancher.environment.REGISTRY_DOMAIN xxxx.yyy to configure the image prefix is now supported.

Like below:

# ros console switch ubuntu
Switching consoles will
1. destroy the current console container
2. log you out
3. restart Docker
Continue [y/N]: y
ERRO[0003] Missing the image: Error: No such image: registry.cn-hangzhou.aliyuncs.com/rancher/os-ubuntuconsole:v1.3.0
Pulling console (registry.cn-hangzhou.aliyuncs.com/rancher/os-ubuntuconsole:v1.3.0)...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants