Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a bootc centos stream 9 host #1859

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ianballou
Copy link
Contributor

@ianballou ianballou commented Sep 26, 2024

I built a base CentOS 9 Stream bootc host and uploaded it as a box to https://portal.cloud.hashicorp.com/services/vagrant/registries/katello/boxes/centos-stream9-bootc/versions/2025.0925.1700?project_id=08e72f3b-c08f-4707-a94b-96f7464fbf9a

It's exposed here in forklift. There are some caveats:

  1. I had to find the raw download link because Fedora's current version of Vagrant doesn't seem to know how to connect to the new Vagrant registry in the Hashicorp cloud (https://app.daily.dev/posts/vagrant-cloud-is-moving-to-hcp-s6pzswzuc)
  2. Bringing the machine up fails with mkdir: cannot create directory ‘/vagrant’: Read-only file system because / is read-only on bootc hosts.
    -> I tried disabling the syncing via synced_folders in the yaml file, but it was ignored. I'm curious if anyone has any other ideas for disabling the default rsyncing for a single host.

@ianballou
Copy link
Contributor Author

Currently planning on trying out a newer vagrant RPM to see if it knows how to download from the new hashicorp cloud box registry.

@ianballou
Copy link
Contributor Author

I confirmed that newer vagrant versions (2.4.1) can install boxes from the new hashicorp registry.

@ehelms
Copy link
Member

ehelms commented Oct 23, 2024

I can download it with vagrant-2.3.4-3.fc39.noarch, but the /vagrant issue is harder. Could we opt for a different strategy using bootc switch on a regular VMs?

@ianballou
Copy link
Contributor Author

I can download it with vagrant-2.3.4-3.fc39.noarch, but the /vagrant issue is harder. Could we opt for a different strategy using bootc switch on a regular VMs?

That's an interesting idea, I'll need to test that out and see how easy it is.

@ianballou
Copy link
Contributor Author

The "regular" VM would have to be an ostree system, which would have the same issues as this bootc VM. The best path forward would likely be to figure out how to stop this NFS mounting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants