21–30 of 34 posts
You can also achieve this with your current system > nix-build ' ' -A vm -I nixpkgs=channel:nixos-25.05 -I nixos-config=./configuration.nix I use nixos btw
Can this do vmdk format?
`nixos-rebuild build-image --image-variant vmware`
See https://nixos.org/manual/nixos/stable/#sec-image-nixos-rebui...
> A container for deploying bootable container images. ...as long as the images are in the Red Hat family (Fedora, CentOS Stream, RHEL).
I wonder which gets more actual usage, this project or linuxkit. Does anyone have experience worth sharing with both?
Also, bootc is a basis for the Universal Blue family of distros, especially Bazzite, which is very popular with gamers.
> A container for deploying bootable container images. ...as long as the images are in the Red Hat family (Fedora, CentOS Stream, RHEL).
Roman Shtylman has an example of using a Dockerfile to produce a rootfs for the Jetson Nano: https://github.com/defunctzombie/jetson-nano-image-maker (2022) I've always been hesitant to use this method over debootstrap: the Ubuntu container images ("FROM ubuntu:20.04") are created from a tarball that Ubuntu's convoluted CI system spits out and I'm not confident I understand if it's somehow suitable only for a contain…
https://github.com/systemd/mkosi
However beware that they break backwards compatibility almost every 6 months. This is probably the most backwards-incompable project I know, you can't rely that the minor version update won't break your projects.
We also have a GUI for trying this out! https://github.com/podman-desktop/extension-bootc We’re also starting to see other projects adopt a “OS as a Container image” such as Bazzite: https://bazzite.gg/ using bootc :) Feel free to ask any questions!
Why swap from the OSTree storage to OCI? Doesn't that negate the space saving offered by OSTree having a content addressable store.
> A container for deploying bootable container images. ...as long as the images are in the Red Hat family (Fedora, CentOS Stream, RHEL).
> A container for deploying bootable container images. ...as long as the images are in the Red Hat family (Fedora, CentOS Stream, RHEL).
I was going to try this to perhaps use it in production. Turns out the RHEL clones like Alma or Rocky doesn't have this thing in production-ready grade. All options you have now are owned by Red Hat themselves.
I wonder which gets more actual usage, this project or linuxkit. Does anyone have experience worth sharing with both?
If I had to wager a guess, bootc might get more actual use now that it's supported in RHEL 9.6 and 10 as "image mode". It's an exciting piece of technology, especially from the perspective of a platform engineer. Also, bootc is a basis for the Universal Blue family of distros, especially Bazzite, which is very popular with gamers.
I thought of the underlying tech for those other distros being ostree more than anything but this is the better interpretation.
Does bootc-image-builder build Native Containers? Do Native Containers work as VM images that can be stored in an OCI Image/Artifact/Package Registry? I've been mentioning Native Containers since I realized that was how bazzite works now. Is vagrant necessary anymore if host, vm, and container images can all be signed and stored in an OCI Image store? From https://news.ycombinator.com/item?id=44137501 re: Firecracker…
What does "native containers" mean in this context?
From https://coreos.github.io/rpm-ostree/container/#ostree-native... :
> rpm-ostree inherits work in ostree-rs-ext to create “container native ostree” functionality. This elevates OCI/docker containers to be natively supported as a transport mechanism for bootable operating systems.
I think it means simplification of complexity and unnecessary re-duplication.