Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Relationship between bootc install and coreos-installer #2015

Answered by cgwalters
mitiemann asked this question in Q&A
Discussion options

Is there any plan to replace/base coreos-installer with/on bootc install?

My context: I plan to base an "embedded OS" on container technology. I have successfully prototyped a system, using coreos-installer to boot strap a bare metal install and then switching to my custom OS using bootc switch. I am now planning how to make this process easily repeatable for more bare metal installs on a small fleet of machines. Since coreos-installer uses ignition and bootc completely relies on container images, I'm wondering which route I should take for embedding/distributing secrets, and, hence, whether I should look more into how to do it with ignition or whether I should try to build isos/use bootc install --to-disk. But maybe I'm not thinking about this in the right way?

Any feedback welcome :-)

You must be logged in to vote

CoreOS is working to align increasingly with bootc. A related issue here is coreos/fedora-coreos-tracker#1906

I'm wondering which route I should take for embedding/distributing secrets,

Yes this is a complex topic. The big thing here is CoreOS tooling is historically not really designed to be forked - it's intended to be a "golden image" OS (and typically secrets come from remote ignition).

There's no one mechanism for secrets; in my experience it bifurcates heavily based on environment (bare metal, cloud and which particular cloud etc).

Replies: 1 comment

Comment options

CoreOS is working to align increasingly with bootc. A related issue here is coreos/fedora-coreos-tracker#1906

I'm wondering which route I should take for embedding/distributing secrets,

Yes this is a complex topic. The big thing here is CoreOS tooling is historically not really designed to be forked - it's intended to be a "golden image" OS (and typically secrets come from remote ignition).

There's no one mechanism for secrets; in my experience it bifurcates heavily based on environment (bare metal, cloud and which particular cloud etc).

You must be logged in to vote
0 replies
Answer selected by mitiemann
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet

AltStyle によって変換されたページ (->オリジナル) /