Description of problem:
'create a client configuration RPM' doesn't ask a user to specify port to serve Docker content on, and there is a separate option to 'create a docker client configuration RPM'. Meanwhile 'create an atomic client configuration package' asks to specify a port to serve Docker content on. Apparently, it shouldn't.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. e generate an entitlement certificate
2. o create an atomic client configuration package
rhui (client) => o
Full path to local directory in which the client configuration files generated by this tool
should be stored (if this directory does not exist, it will be created):
Name of the tar file (excluding extension):
Full path to the entitlement certificate authorizing the client to access
Full path to the private key for the above entitlement certificate:
Port to serve Docker content on (default 5000):
Successfully created client configuration package.
Package tar file can be found at /tmp/
Why not? The tarball then contains these commands:
mkdir -p /etc/docker/certs.d/cds.example.com:5000
cp ./ca.crt /etc/docker/certs.d/cds.example.com:5000/ca.crt
sed -i '/ADD_REGISTRY/s/=.*/='"'"'--add-registry cds.example.com:5000'"'"'/' /etc/sysconfig/docker
This looks like a feature to me.
I mean, install.sh in the tarball contains those commands.
And if the entitlement cert doesn't contain any docker repo?
And some time ago 'c - create a client configuration RPM' also contained that Docker port, but after 'd - create a docker client configuration RPM' was added, it was removed from 'c'. Do you remember you corrected the lib for client conf rpm creation because of that? Commit b2a6bcb.
There are no docker "repos" to include in an entitlement cert (and that's why the docker workflow was split and the test suite was adjusted). Docker containers are mirrored from the Red Hat and served on <haproxy_host>:<port> (port=5000 by default). You don't necessarily have to have a docker container in your RHUI, but my understanding is that it's good to prepare the configuration on the atomic host in case you ever start serving docker containers. Engineering could tell you why they put the prompt for the docker port to the atomic tar creation.
Radek is correct.
The atomic host has docker pre-installed as one of atomic host's primary functions is to host docker containers.
So, to recap:
1) We moved docker to it's own client config setup for client config RPMs by design.
2) We included docker in the atomic host config package as atomic hosts can host docker images as well.
Patrick, thanks for the clarification.