Skip to content

chore: Track support for bootc adoption #504

@fiftydinar

Description

@fiftydinar

Intro

Initially, when starting out, BlueBuild marketed itself as a custom-image tooling for Fedora Atomic only when only rpm-ostree was available.
This is still generally the truth today, even with bootc existing.

However, bootc support for other Linux distributions, aka being distro-agnostic, is having some great progress, thanks to @tulilirockz and other people.

This would be great for BlueBuild, since users could choose whichever Linux distribution they like as the base image. For example, Arch, Debian, Alpine or some other.

We are aware that support for runtime package layering is non-existent in bootc, but I think this one needs to be implemented on per-distro basis and is not something for bootc to handle. We will check progress on that if it exists. In the meantime, for users which miss it, rpm-ostree still exists for Fedora Atomic images.

As a part of the effort to make our custom-image tooling compatible with every Linux offering, we need to prepare and be free of any Fedora Atomic hardcoded stuff.

This issue is made in modules, repo, but it also applies to everything else, like CLI and documentation, so we will track those here too.

You can edit this freely if you find the new issue or if something gets fixed.

Issue tracker

Modules

CLI

Metadata

Metadata

Assignees

No one assigned

    Labels

    breakingIntroduces a breaking change.type: featureBrand new functionality, features, pages, workflows, endpoints, etc.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions