Dan Čermák

Thomas Renninger writes: > Hi, this feature is old, but still it would be very convenient to > have... Indeed it would. > Any chance we get something like this?...

> As of Vagrant 2.3, Vagrant ships with a second executable called vagrant-go. This represents the current state of our work to reimplement Vagrant in Go, as a part of...

> I suspect the API has changed. Do you have any WIP fix or idea on how to fix it? Unfortunately no, as I haven't observed this failure on openSUSE...

@pvalena @jackorp We have been running vagrant with Ruby 3.1 in openSUSE Tumbleweed for about two months now and I haven't heard of any issues so far, except for hitting...

@chrisroberts Could you please take a look?

@chrisroberts @soapy1 @phinze Could you please take a look? Ruby 3.1 is the default on many distributions now and this is now starting to block development with vagrant on these…

> Thanks for the contribution. > > Can you tell me the story behind why you are building k3sup instead of using the binary? I am testing a multi-arch container...

Friendly bump :)

This looks more like an issue with ruby-libvirt failing to compile on your machine. Maybe you can check Clearlinux' build scripts how they build ruby-libvirt?

> Hello, > If it "helps", I have the exact same failures on a fedora-32 box... On Fedora you're best of just using the package from the repos (`dnf install...