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