base operating system for building container images
Hello together, we of the s390x port wanted to start with our existing container images tomcat [0] and httpd [1] to test and enable these ones for s390x, because that does not exist for s390x in registry.opensuse.org at the moment. My question is: Which base operating system is used for building our container images? The reason is, that we were able to reproduce errors (Sysconfig) with SLES SP2 in the LinuxONE Community Cloud. Then we did an upgrade to openSUSE Tumbleweed and we didn't receive any failures any more (without changes in the Dockerfile). You can not receive any background about build failures for special architectures in OBS [2] because all is disabled. Therefore, I wanted to ask for the required environment to reproduce not working container images. Thank you! Best regards, Sarah [0] https://github.com/openSUSE/container-images/tree/main/tomcat [1] https://github.com/openSUSE/container-images/tree/main/httpd [2] https://build.opensuse.org/project/show/openSUSE:Containers:Tumbleweed
On Tue, 2021-07-27 at 13:16 +0200, Sarah Julia Kriesch wrote:
Hello together,
we of the s390x port wanted to start with our existing container images tomcat [0] and httpd [1] to test and enable these ones for s390x, because that does not exist for s390x in registry.opensuse.org at the moment.
My question is: Which base operating system is used for building our container images? The reason is, that we were able to reproduce errors (Sysconfig) with SLES SP2 in the LinuxONE Community Cloud. Then we did an upgrade to openSUSE Tumbleweed and we didn't receive any failures any more (without changes in the Dockerfile). You can not receive any background about build failures for special architectures in OBS [2] because all is disabled. Therefore, I wanted to ask for the required environment to reproduce not working container images.
As you can see from registry.opensuse.org [0] almost all of our Official Containers are built from Tumbleweed the only exceptions I am aware of are - opensuse/leap - opensuse/leap-dnf Meanwhile every other official container produced by the openSUSE Project is built on a Tumbleweed base. I hope this answers your question https://registry.opensuse.org/cgi-bin/cooverview?srch_term=project%3D%5Eopen... -- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
Hi Richard,
Gesendet: Dienstag, 27. Juli 2021 um 13:41 Uhr Von: "Richard Brown" <rbrown@suse.de> An: factory@lists.opensuse.org Betreff: Re: base operating system for building container images
On Tue, 2021-07-27 at 13:16 +0200, Sarah Julia Kriesch wrote:
Hello together,
we of the s390x port wanted to start with our existing container images tomcat [0] and httpd [1] to test and enable these ones for s390x, because that does not exist for s390x in registry.opensuse.org at the moment.
My question is: Which base operating system is used for building our container images? The reason is, that we were able to reproduce errors (Sysconfig) with SLES SP2 in the LinuxONE Community Cloud. Then we did an upgrade to openSUSE Tumbleweed and we didn't receive any failures any more (without changes in the Dockerfile). You can not receive any background about build failures for special architectures in OBS [2] because all is disabled. Therefore, I wanted to ask for the required environment to reproduce not working container images.
As you can see from registry.opensuse.org [0] almost all of our Official Containers are built from Tumbleweed
the only exceptions I am aware of are
- opensuse/leap - opensuse/leap-dnf
Meanwhile every other official container produced by the openSUSE Project is built on a Tumbleweed base.
I don't speak about the "inside" of the container. I know that it is based on openSUSE Tumbleweed. I asked for the building base operating system. Is there also openSUSE Tumbleweed or is openSUSE Kubic, MicroOS, ... used? But it seems, that we didn't make any mistake in our setup for the development environment. These images were not enabled in OBS for our ports.
I hope this answers your question
https://registry.opensuse.org/cgi-bin/cooverview?srch_term=project%3D%5Eopen...
Best regards, Sarah
-- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
On Tue, Jul 27, 2021 at 8:03 AM Sarah Julia Kriesch <ada.lovelace@gmx.de> wrote:
Hi Richard,
Gesendet: Dienstag, 27. Juli 2021 um 13:41 Uhr Von: "Richard Brown" <rbrown@suse.de> An: factory@lists.opensuse.org Betreff: Re: base operating system for building container images
On Tue, 2021-07-27 at 13:16 +0200, Sarah Julia Kriesch wrote:
Hello together,
we of the s390x port wanted to start with our existing container images tomcat [0] and httpd [1] to test and enable these ones for s390x, because that does not exist for s390x in registry.opensuse.org at the moment.
My question is: Which base operating system is used for building our container images? The reason is, that we were able to reproduce errors (Sysconfig) with SLES SP2 in the LinuxONE Community Cloud. Then we did an upgrade to openSUSE Tumbleweed and we didn't receive any failures any more (without changes in the Dockerfile). You can not receive any background about build failures for special architectures in OBS [2] because all is disabled. Therefore, I wanted to ask for the required environment to reproduce not working container images.
As you can see from registry.opensuse.org [0] almost all of our Official Containers are built from Tumbleweed
the only exceptions I am aware of are
- opensuse/leap - opensuse/leap-dnf
Meanwhile every other official container produced by the openSUSE Project is built on a Tumbleweed base.
I don't speak about the "inside" of the container. I know that it is based on openSUSE Tumbleweed. I asked for the building base operating system. Is there also openSUSE Tumbleweed or is openSUSE Kubic, MicroOS, ... used? But it seems, that we didn't make any mistake in our setup for the development environment. These images were not enabled in OBS for our ports.
There are only two real distributions of openSUSE: openSUSE Tumbleweed and openSUSE Leap. Everything else is just a variant of one of those two (generally openSUSE Tumbleweed). -- 真実はいつも一つ！/ Always, there's only one truth!
On Tue, Jul 27, Neal Gompa wrote:
There are only two real distributions of openSUSE: openSUSE Tumbleweed and openSUSE Leap. Everything else is just a variant of one of those two (generally openSUSE Tumbleweed).
I think she tries to build the containers on a SLES 15 SP2 system, which means SLES 15 SP2 RPMs will be installed on top of a Tumbleweed base container, if they don't adjust the Dockerfile. And this will of course not work dependency wise. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg)
On Tue, Jul 27, 2021 at 8:30 AM Thorsten Kukuk <kukuk@suse.de> wrote:
On Tue, Jul 27, Neal Gompa wrote:
There are only two real distributions of openSUSE: openSUSE Tumbleweed and openSUSE Leap. Everything else is just a variant of one of those two (generally openSUSE Tumbleweed).
I think she tries to build the containers on a SLES 15 SP2 system, which means SLES 15 SP2 RPMs will be installed on top of a Tumbleweed base container, if they don't adjust the Dockerfile. And this will of course not work dependency wise.
Oh, well yeah, that's not going to work very well. :) -- 真実はいつも一つ！/ Always, there's only one truth!
On Tue, Jul 27, Sarah Julia Kriesch wrote:
I don't speak about the "inside" of the container. I know that it is based on openSUSE Tumbleweed. I asked for the building base operating system. Is there also openSUSE Tumbleweed or is openSUSE Kubic, MicroOS, ... used? But it seems, that we didn't make any mistake in our setup for the development environment. These images were not enabled in OBS for our ports.
Sorry, but a base operarting system is not involved in building container. Do you mean you want to run an openSUSE Tumbleweed container on SLES 15 SP2? Or do you mean you want to build one of the containers on SLES 15 SP2? So if you enable that container to build on SLES 15 SP2, SLES 15 SP2 RPMs will be put inside the derived container. The base container is still was you reference in the Dockerfile. There are base containers, applications and derived containers, but not a Base OS. Thorsten
I hope this answers your question
https://registry.opensuse.org/cgi-bin/cooverview?srch_term=project%3D%5Eopen...
Best regards, Sarah
-- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg)
Gesendet: Dienstag, 27. Juli 2021 um 14:27 Uhr Von: "Thorsten Kukuk" <kukuk@suse.de> An: factory@lists.opensuse.org Betreff: Re: base operating system for building container images
On Tue, Jul 27, Sarah Julia Kriesch wrote:
I don't speak about the "inside" of the container. I know that it is based on openSUSE Tumbleweed. I asked for the building base operating system. Is there also openSUSE Tumbleweed or is openSUSE Kubic, MicroOS, ... used? But it seems, that we didn't make any mistake in our setup for the development environment. These images were not enabled in OBS for our ports.
Sorry, but a base operarting system is not involved in building container. Do you mean you want to run an openSUSE Tumbleweed container on SLES 15 SP2?
Or do you mean you want to build one of the containers on SLES 15 SP2? Exactly! That has been failed and worked on openSUSE Tumbleweed. The LinuxONE Community Cloud provides only VMs with SLES 15 SP2 (no community distributions). We were lucky to have multiple VMs sponsored by IBM for this day and we have upgraded SLES 15 SP2 to openSUSE Tumbleweed.
Therefore, we wanted to compare the behavior, because we were not able to reproduce any error messages with openSUSE Tumbleweed and an installed docker for building images in our development environment. Therefore, I thought about any requirements for the development environment, if no s390x images can be built via OBS (and published) and we don't receive any error messages on openSUSE Tumbleweed.
So if you enable that container to build on SLES 15 SP2, SLES 15 SP2 RPMs will be put inside the derived container. The base container is still was you reference in the Dockerfile.
There are base containers, applications and derived containers, but not a Base OS. Ok. I asked this question, because "as default" you should be able to reproduce "Failed builds" with openSUSE Tumbleweed and installed docker or Podman. It seems, that we didn't make any mistakes. Ports for Dockerfile buildings for our ports were not enabled in OBS and that was the reason for no container images for s390x and other port architectures. We can see more container images (hopefully) tomorrow.:-)
Sarah
Thorsten
I hope this answers your question
https://registry.opensuse.org/cgi-bin/cooverview?srch_term=project%3D%5Eopen...
Best regards, Sarah
-- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer
-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg)
participants (4)
-
Neal Gompa -
Richard Brown -
Sarah Julia Kriesch -
Thorsten Kukuk