Bug 1245145

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Peter,

Thanks for the feedback/request. This will have to be evaluated in the next planning phase of the documentation and I will update this bug once I know when we can get this assigned. 

Regards,
Hayley Hudgeons

Resetting the QA contact.

Assigning to Melanie for review.

Melanie - this is another detailed bug in a similar vein to the one on building cloud images. I'm not sure at this stage if we need to go into as much detail on building the container images themselves if that is already covered elsewhere, but instructions on how to incorporate images into Satellite infrastructure as requested would be highly beneficial.

We already have some content on adding container compute resources and adding images, but a pointer to a reference on building images and some content on each of the other points from errata management onwards would be a great addition. This feels like it would be best positioned in the 'Managing Containers' section of the Managing Hosts guide.

Hi Peter, 

Apologies for the delay in solving this bug. 

I have been going through the bug trying to understand what aspect you
would like covered.

I worked through the following guides from Red Hat Enterprise Linux [1][2], with success and could pull images into Docker containers and update them.

From a Satellite perspective, a Docker registry is handled with Content Views.

Satellite itself does not compose or create images, but you can store the Docker images in Content Views. You can then create or update images and publish a new Content View version if there are errata you need to apply.

From the RHEL documentation [1] I found that I could use yum update in a running container, and then save it as a new container image after the updates in a Satellite Content View.

We have a pre-existing section in the Satellite Content Management guide  about how to manage container images in Satellite[3]


There is a sub section that you might find particularly interesting:
10.3. Managing Container Images with Content Views

I will also include a link to provisioning containers in Satellite via Red Hat Atomic host set up as a compute resource[4]


Finally, is there another work flow you have in mind? If what I have outlined here is missing the point, please let me know, so that I can try to resolve this for you.

Thank you,

Melanie


[1]

https://access.redhat.com/documentation/en/openshift-container-platform/3.3/single/creating-images/

[2]

https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/7/single/getting-started-with-containers/

[3]

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/content_management_guide/managing_container_images

[4]


https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/provisioning_guide/provisioning_containers

Good documentattion sofar.

What I still miss is how to use an Existing Published ContentView with RPMs and Puppet modules to build a Docker image.

To use the content view of Sat6 in the image build process you need the entitlement etc.

It is related to Sat6 and Mock, but there one can cheat to use the entitlement from the host in the mock environment. Atricle https://access.redhat.com/blogs/1169563/posts/2191211

As i have no needs to build Containers in the foreseable future it is ok to close this BZ

Thanks
Peter