[opensuse-factory] Submitting Kata Containers to Factory
Hi, I would like to like to submit to Factory the packages for Kata Containers (something similar to what's now in devel:kubic:katacontainers). TL,DR about Kata: it's a way to run containers inside VMs. The VMs needs tailored built KVM kernel and image. For the kernel, I plan to adapt kernel-kvmsmall, I just need few changes to the existing config file. For the image, now I am building it using kiwi, and wrapping it in a RPM using a kiwi_post_run hook on OBS. To achieve this, I needed to update the project config to have a containment-rpm package pre-installed, taking care of the RPM wrapping and of some image customization. Would having this kind of image in Factory, wrapped in an RPM, something acceptable? If so, what would be the correct way to submit it, given the way such image is built? If not, and you have other ideas to distribute the image built on OBS in a package-like way (e.g. installable with zypper) I am open to those. Thanks Marco -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, Am Donnerstag, 6. Juni 2019, 13:07:09 CEST schrieb Marco Vedovati:
Hi, I would like to like to submit to Factory the packages for Kata Containers (something similar to what's now in devel:kubic:katacontainers).
TL,DR about Kata: it's a way to run containers inside VMs. The VMs needs tailored built KVM kernel and image.
For the kernel, I plan to adapt kernel-kvmsmall, I just need few changes to the existing config file.
For the image, now I am building it using kiwi, and wrapping it in a RPM using a kiwi_post_run hook on OBS. To achieve this, I needed to update the project config to have a containment-rpm package pre-installed, taking care of the RPM wrapping and of some image customization.
containment-rpm-docker again? I was happy to get that dropped half a year ago.
Would having this kind of image in Factory, wrapped in an RPM, something acceptable? If so, what would be the correct way to submit it, given the way such image is built?
Having a kiwi_post_run hook defined globally (for kiwi-image:lxc) in openSUSE:Factory won't work, so the only option for this would be to have a new openSUSE:Factory:Kata prj or something like that. Alternatives to the prjconf change would be a new <!-- OBS-BuildRequires: --> comment in the .kiwi file or a new attribute in the XML, but that smells a bit like a hack.
If not, and you have other ideas to distribute the image built on OBS in a package-like way (e.g. installable with zypper) I am open to those.
Can you somehow make use of registry.opensuse.org? Cheers, Fabian
Thanks Marco
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 6/6/19 1:39 PM, Fabian Vogt wrote:
containment-rpm-docker again? I was happy to get that dropped half a year ago.
Not something I am a proud of :) That was the most straight forward tool to for my problem.
so the only option for this would be to have a new openSUSE:Factory:Kata prj or something like that.
This is to build the RPM in a subproject, and then have an _aggregate link to openSUSE:Factory?
Alternatives to the prjconf change would be a new <!-- OBS-BuildRequires: --> comment in the .kiwi file or a new attribute in the XML, but that smells a bit like a hack.
Or also add to Kiwi a way to generate RPM without the need of an extra containment package.
Can you somehow make use of registry.opensuse.org?
Nope, because this is a VM image, like QCOW, but without the "cow" as it's read-only for the guest.
Cheers, Fabian
Thanks Marco
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, Am Donnerstag, 6. Juni 2019, 16:07:01 CEST schrieb Marco Vedovati:
On 6/6/19 1:39 PM, Fabian Vogt wrote:
containment-rpm-docker again? I was happy to get that dropped half a year ago.
Not something I am a proud of :) That was the most straight forward tool to for my problem.
so the only option for this would be to have a new openSUSE:Factory:Kata prj or something like that.
This is to build the RPM in a subproject, and then have an _aggregate link to openSUSE:Factory?
Almost, just without _aggregates. The FTP tree (=OSS repo) can be configured to pull from other OBS projects as well.
Alternatives to the prjconf change would be a new <!-- OBS-BuildRequires: --> comment in the .kiwi file or a new attribute in the XML, but that smells a bit like a hack.
Or also add to Kiwi a way to generate RPM without the need of an extra containment package.
Yes, but I don't think that's going to be implemented - it would be a fairly complex change in kiwi for something that's not directly image building. Also, shipping containers in RPM is something that should be avoided. Containers are data and not part of the operating system and should therefore be installed in /var. Otherwise you'd lose all containers on a system rollback. That's something using a service like the registry also avoids.
Can you somehow make use of registry.opensuse.org?
Nope, because this is a VM image, like QCOW, but without the "cow" as it's read-only for the guest.
The blob store doesn't care about the format, so it might be possible to use the registry API for katacontainer images as well. Cheers, Fabian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 6/6/19 4:13 PM, Fabian Vogt wrote:
so the only option for this would be to have a new openSUSE:Factory:Kata prj or something like that.
This is to build the RPM in a subproject, and then have an _aggregate link to openSUSE:Factory?
Almost, just without _aggregates. The FTP tree (=OSS repo) can be configured to pull from other OBS projects as well.
This sounds the better (and only) option to me. To whom can I address the request for such subproject?
Or also add to Kiwi a way to generate RPM without the need of an extra containment package.
Yes, but I don't think that's going to be implemented - it would be a fairly complex change in kiwi for something that's not directly image building.
Also, shipping containers in RPM is something that should be avoided. Containers are data and not part of the operating system and should therefore be installed in /var. Otherwise you'd lose all containers on a system rollback. That's something using a service like the registry also avoids.
Can you somehow make use of registry.opensuse.org?
Nope, because this is a VM image, like QCOW, but without the "cow" as it's read-only for the guest.
The blob store doesn't care about the format, so it might be possible to use the registry API for katacontainer images as well. I am afraid this solution would create confusion, as users may either
In case of the image under discussion, losing it would be the expected behaviour, as it's something tightly coupled with the runtime, and useless without it. think that's a container image, and they would expect to directly use that to run containers. Thanks Marco -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, Am Donnerstag, 6. Juni 2019, 18:07:49 CEST schrieb Marco Vedovati:
On 6/6/19 4:13 PM, Fabian Vogt wrote:
so the only option for this would be to have a new openSUSE:Factory:Kata prj or something like that.
This is to build the RPM in a subproject, and then have an _aggregate link to openSUSE:Factory?
Almost, just without _aggregates. The FTP tree (=OSS repo) can be configured to pull from other OBS projects as well.
This sounds the better (and only) option to me. To whom can I address the request for such subproject?
Dominique aka DimStar
Or also add to Kiwi a way to generate RPM without the need of an extra containment package.
Yes, but I don't think that's going to be implemented - it would be a fairly complex change in kiwi for something that's not directly image building.
Also, shipping containers in RPM is something that should be avoided. Containers are data and not part of the operating system and should therefore be installed in /var. Otherwise you'd lose all containers on a system rollback. That's something using a service like the registry also avoids.
In case of the image under discussion, losing it would be the expected behaviour, as it's something tightly coupled with the runtime, and useless without it.
Can you somehow make use of registry.opensuse.org?
Nope, because this is a VM image, like QCOW, but without the "cow" as it's read-only for the guest.
The blob store doesn't care about the format, so it might be possible to use the registry API for katacontainer images as well. I am afraid this solution would create confusion, as users may either think that's a container image,
I also thought that's what you're talking about (you just wrote "image"). If you're not, just disregard what I wrote. Cheers, Fabian
and they would expect to directly use that to run containers.
Thanks Marco
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Fabian Vogt -
Marco Vedovati