4 ms·

This isn't a "side project" (I'm not going to make money from it, and it's also something that I work on at my job), but I've been working on umoci[1] which is

by cyphar 10y ago

This isn't a "side project" (I'm not going to make money from it, and it's also something that I work on at my job), but I've been working on umoci[1] which is a way to create and manipulate OCI container images. At (open)SUSE we're planning on using it to create container images inside the Open Build Service. I've also got a few ideas about RPM distribution of OCI images that I'm quite excited about, and hopefully I'll have some code that works soon. [1]: https://github.com/cyphar/umoci https://github.com/cyphar/umoci

atmosx 10y ago
This sounds interesting but the use case seems very specific to your internal infratstruture and tooling. Can you elaborate a bit on use cases?
- cyphar 10y ago
  > This sounds interesting but the use case seems very specific to your internal infratstruture and tooling. This is actually also part of the openSUSE project[1], and it's all free software. The Open Build Service[2] supports several package formats and distributions (Arch Linux's PKGBUILD, Fedora/RedHat's RPMs, openSUSE/SUSE's RPMs, Debian/Ubuntu's debs). > Can you elaborate a bit on use cases? Currently at SUSE we're working on a new product for running Kubernetes on top of our distribution. One of the important pieces is building and distributing official SUSE images (as well as customers distributing images). But this code will be a part of the public Open Build Service instance, so everyone will be able to use it. And SUSE customers will also be able to use to to create their own images. Effectively the "cool thing" is that you can create OCI images without needing to use something like Docker -- it's all just modifying a root filesystem and umoci will generate the diff layers for you. I'm also working on distributing OCI images through RPMs, which may end up being a really cool way of distributing images (because all of SUSE's tooling is built to work with RPMs). [1]: http://openbuildservice.org/ http://openbuildservice.org/ [2]: https://build.opensuse.org/ https://build.opensuse.org/

by cyphar 10y ago

atmosx 10y ago

This sounds interesting but the use case seems very specific to your internal infratstruture and tooling. Can you elaborate a bit on use cases?

cyphar 10y ago
> This sounds interesting but the use case seems very specific to your internal infratstruture and tooling. This is actually also part of the openSUSE project[1], and it's all free software. The Open Build Service[2] supports several package formats and distributions (Arch Linux's PKGBUILD, Fedora/RedHat's RPMs, openSUSE/SUSE's RPMs, Debian/Ubuntu's debs). > Can you elaborate a bit on use cases? Currently at SUSE we're working on a new product for running Kubernetes on top of our distribution. One of the important pieces is building and distributing official SUSE images (as well as customers distributing images). But this code will be a part of the public Open Build Service instance, so everyone will be able to use it. And SUSE customers will also be able to use to to create their own images. Effectively the "cool thing" is that you can create OCI images without needing to use something like Docker -- it's all just modifying a root filesystem and umoci will generate the diff layers for you. I'm also working on distributing OCI images through RPMs, which may end up being a really cool way of distributing images (because all of SUSE's tooling is built to work with RPMs). [1]: http://openbuildservice.org/ http://openbuildservice.org/ [2]: https://build.opensuse.org/ https://build.opensuse.org/