On Fri, Aug 16, Thomas Bechtold wrote:
On 8/13/19 1:35 PM, Thorsten Kukuk wrote:
On Tue, Aug 13, Thomas Bechtold wrote:
Is it possible (like for RPM packages) to build a container for different distros (eg. SLE_15_SP1 and openSUSE_Leap_15.1) within the same OBS package? Maybe with kiwi profiles and multibuild? Or what's the recommended way to maintain containers for multiple distros?
This would be more a question for our kiwi and OBS experts, I don't know.
- should a container (eg mariadb) be in the devel project (server:database for mariadb) and submitted to openSUSE:Factory ?
For openSUSE Kubic we created devel:kubic:containers Since you need to setup building containers correct in the devel project, I would create a devel project only for building containers and not enable it in many different devel projects.
ok. I guess we create then something in the Cloud:OpenStack: namespace on OBS for the openstack specific containers. But what about a container like mariadb? Where should be the devel project for that container?
The official base container for tumbleweed is build here: https://build.opensuse.org/project/show/Virtualization:containers:images:ope... I think that would fit very well for generic openSUSE Tumbleweed containers, ask the project maintainers what they think.
- do we have a naming schema for the container packages (eg. mariadb-container or mariadb-image)?
For Kubic we are using kubic-*-image For Tumbleweed we are using tumbleweed-*-image
You should think about the namespace on the registry. If this containers are generic useable, it should go into the registry.opensuse.org/opensuse namespace. If this containers are only useable for your Cloud product, we should maybe discuss a new namespace for this.
And if the containers are generic useable, please make sure, the containers build for x86-64, aarch64, power64le and s390x.
One more question about generic usable containers - do we try to be compatible (basically using the docker-entrypoint.sh scripts from github.com/docker-library) with the "official" dockerhub containers? That's something we might need because some helm charts rely on ENV vars that can be set and are then used in the docker-entrypoint.sh script.
This really depends. If you want to replace containers we would else use from docker hub, you need to make our container compatible. If you want to have/need something different, you cannot make it compatible... Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org