Open ianballou opened 2 months ago
Currently planning on trying out a newer vagrant RPM to see if it knows how to download from the new hashicorp cloud box registry.
I confirmed that newer vagrant versions (2.4.1) can install boxes from the new hashicorp registry.
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?
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 usingbootc switch
on a regular VMs?
That's an interesting idea, I'll need to test that out and see how easy it is.
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.
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 withmkdir: cannot create directory ‘/vagrant’: Read-only file system
because/
is read-only on bootc hosts. -> I tried disabling the syncing viasynced_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.