Container base images and style

[mayrstefan]

Looking into the containers directory we find two different image styles:

1. containers using the init image are still based on Leap 15.6 which will EOL soon
2. the proxy containers use the more current 15.7 BCI images but have some oddities

What is the current roadmap for the base image? Will they change to Tumbleweed or to BCI? If BCI is targeted - version 15.7 or 16.0?

About the oddities of the proxy images:

• add_repos.sh seems outdated - it adds empty Leap 15.3 repositores
• remove_unused.sh ist also strange: why does it delete zypper? When creating the slim image it is part of the base image again
• the style used in the Dockerfile seems very old: now it is best practice to combine multiple run commands like in the server image
• COPY commands are followed by RUN chown or chmod commands - which could also be done with the COPY command
• What is the purpose of a multi stage build when the "slim" image contains literally everything from the "base" stage? It only flattens the number of layers
• which brings us the an oddity of the server image: the zypper clean --all is missing after the package installation and the separate RUN command to delete logs is just hiding them - they still exist in the previous layer (also the suseconnect log is missing from the delete list)

So before submitting any pull requests: what is your plan on how those images should be created? What is the reference and what should we pay attention for?

[rjmateus]

Hey @mayrstefan

We are now currently analyzing it and we are considering moving all uyuni images to 15.7 BCI images. We are checking if we don't have any limitations or cause issues to users. For now, we are targeting 15.7, but we will eventually move to 16.x

Proxy images were the first's we developed, and those need to be revisited. @cbosdo do you have any insides on this ?

[cbosdo]

Hey @mayrstefan

We are now currently analyzing it and we are considering moving all uyuni images to 15.7 BCI images. We are checking if we don't have any limitations or cause issues to users. For now, we are targeting 15.7, but we will eventually move to 16.x

Proxy images were the first's we developed, and those need to be revisited. @cbosdo do you have any insides on this ?

We need to revisit them all, but I don't have that much time to spend on that these days. I would happily review a PR fixing some of the oddities.

[mayrstefan]

I tried a PR: #11106 . But I could only partially test them. What is the PRODUCT_REPO that is used to install the uyuni packages?

[cbosdo]

The add_repos.sh scripts can surely be dropped: it was made to build the containers locally in the very first versions. I am not even sure this still works as we always build them with OBS anyway