-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need a way to specify custom directories for rhsm configuration #186
Comments
I would think having it point to /etc/rhsm-containers would be better then latest. |
How about enhancing the secrets patch to look in both Then all you'd need to do is |
I am fine with this although I would prefer something generic like /etc/container/rhel/secrets. |
+1 |
@rhatdan @cgwalters both suggestions are good and will work for me. |
@runcom can you modify the secrets patch to handle this? |
@rhatdan sure I can |
@runcom, can this be closed? |
Patch moby#6075 adds support to docker to specify "secret" files to be injected in a container. As of today's Atomic Hosts when one does
docker run -it registry.access.redhat.com/rhel7
the secrets files are copied over and injected into the container from/usr/share/rhel/secrets
. This enables subscription manager to run inside containers as desired.On the atomic host we see the forllowing
So consider the case where you want the /etc/rhsm on the host to be different from the /etc/rhsm inside the container. It could be something basic like "the rhsm base url for yum repos is different from base url for atomic ostree repos" OR "we want to use different entitlement models and hide access to certain repos on hosts vs containers". The above configuration will make it impossible to change that because
/usr/share/rhel/secrets/rhsm
is a read-only link . The symlink there cannot be redirected.The
/etc/rhsm
conf symlinked above specifically points hosts rhsm conf. We cannot have separate configurations for hosts and containers.In short we need something like this
What this would enable is for one to change what /etc/rhsm-latest points to and specify an alternate configuration for the container while preserving the default behavior when desired.
The text was updated successfully, but these errors were encountered: