home.social

#vagrant — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #vagrant, aggregated by home.social.

fetched live
  1. Dla Politechnika Bydgoska im. Jana i Jędrzeja Śniadeckich szykuję dedykowane szkolenie, więc przy okazji dokumentuję #vagrant. Fajne narzędzie.....

  2. Oups, looks like #Vagrant boxes registry will cease to exist very soon: developer.hashicorp.com/hcp/do

    Too bad that there is still no 1:1 ecosystem replacement with a proper FOSS license. 🫠

  3. I think it is really sad that with the license change vagrant has dropped in everybody's perception. There are many projects no longer caring about vagrant (due to the reduced number of users) and no longer building or publishing vagrant boxes. Alpine is stuck at 3.19, Debian13 download is broken for months, Fedora is stuck at 39. (I never could get the openSUSE publisher working, so I take the blame for that).

    I still like the vagrant workflow, having a easy way to create shareable environments. I really like it in combination with Ansible to easily have demo setups or playgrounds.

    This far I did not find a replacement. Alternatives are either not as universally usable or are lacking features like the Ansible integration. I'll keep on looking...

    #Vagrant #DevOps #AdminLife #HellYeah #Hashicorp

  4. @jpmens I use it almost on a daily basis. Mostly for small demo setups showcasing a new piece of software I found or for playing around with things.

    All of my setups are vagrant + libvirt + Ansible.
    Most are with k3s, some with Podman Quadlets, some run things natively on the VMs...

    I have not yet found a good replacement.

    #Vagrant

  5. Rediscovering Vagrant after 15 years of not using it and realising it can be really damn useful... #Vagrant

  6. Dear devs, is Vagrant in 2026 still a thing to set up dev environments ?
    Like, if I don't wanna set up php and all the tools on my own machine....?
    Or you do it all with docker?

    #dev #developerlife #vagrant #docker #devsetup #developer #development #developmentsetup

  7. Bringing machine 'default' up with 'libvirt' provider...
    [fog][WARNING] Unrecognized arguments: libvirt_ip_command
    ==> default: Box 'generic/freebsd15' could not be found. Attempting to find and install...
    default: Box Provider: libvirt
    default: Box Version: >= 0
    The box 'generic/freebsd15' could not be found or could not be accessed in the remote catalog.

    Anyone knows if there are plans to provide more images for vagrant and FreeBSD 15 ?

    #freebsd #libvirt #vagrant

  8. #Vagrant free software dismissal is starting to get a problem. No trixie boxes etc ..

    What are your alternatives for ansible test deployments?

    lima?

  9. I've tried to run it under #Wine, but I could not make it work. The game only runs in some specific resolutions and color 16-bit color depth (which I managed to work around using Xephyr). I managed to install it under Wine and have it run. But I could not go farther than the initial screen.

    So I installed #Windows 98 SE into a VM. Since I was at it, I created a #Vagrant image anyone can use. It has working display and audio drivers. Link below.

    This way I (and whoever) can quickly launch a VM and install games from this era without having to deal with the quirks or Wine.

    portal.cloud.hashicorp.com/vag

    #games #pcgaming #trains #linuxgaming

  10. Can't find a vagrant image fedora/42-cloud-base

    41 is present anyone knows why 42 is absent?

    #fedora #vagrant

  11. So I have been playing with the WriteFreely blog system. To check out if this would work for the use case I was asked about.

    I built a vagrant-libvirt setup (using the usual vagrant/libvirt/Ansible approach) as well as a package for openSUSE. The setup uses my package on Leap and Tumbleweed or the upstream binary on a third branch. Another branch will set this up behind a Nginx reverse proxy.

    I'll give the package a decent spin and then send it to a devel project to get it into Tumbleweed.

    Here you are, have a lot of fun...
    codeberg.org/johanneskastl/wri
    github.com/johanneskastl/write

    #WriteFreely #blog #CMS #vagrant #libvirt #ansible #openSUSE #Tumbleweed #Leap #HellYeah

  12. Hey @fedora,

    are there any plans to release the #Vagrant box for #Fedora42 to app.vagrantup.com?

    There is already a box available on the Fedora server, but without metadata (which makes updates hard...).

    download.fedoraproject.org/pub

    (I know Vagrant is no longer used widely and Hashicorp messed up with the whole licensing trouble, but having an existing box available easiy would really be appreciated nontheless...)

    Have a nice day, everyone!

    #Vagrant #Fedora #libvirt

  13. Having fun with the Ghost CMS.

    The installation is only supported on Ubuntu. And is tailored to Ubuntu and thus does not recognized Nginx installations on other operating systems.

    I put together a vagrant-libvirt setup using Ansible that does the tricky bits itself. Currently supporting AlmaLinux 10, openSUSE Tumbleweed and Fedora 41, see the different branches.

    This is a "production" setup of Ghost, i.e. using a MariaDB database instead of sqlite3.

    codeberg.org/johanneskastl/gho
    github.com/johanneskastl/ghost

    Have a lot of fun...

    #GhostCMS #vagrant #libvirt #Ansible #AlmaLinux #openSUSE #Fedora #HellYeah

  14. Another day, another vagrant-libvirt setup.

    This time for MariaDB, with a server VM and a client VM. As usual, vagrant, libvirt and Ansible do the heavy lifting.

    codeberg.org/johanneskastl/mar
    github.com/johanneskastl/maria

    Have a lot of fun...

    #MariaDB #Ansible #vagrant #libvirt #HellYeah #DevOps

  15. In case you want to get your hands dirty with Traefik, Kubernetes and the new GatewayAPI, I got you covered.

    Here is another vagrant-libvirt setup that has #k3s, #Traefik and a #Nginx deployment. Instead of using a #Kubernetes #ingress or a Traefik ingressroute, this setup uses the #GatewayAPI resources like Gateways and HTTPRoutes.

    codeberg.org/johanneskastl/tra
    github.com/johanneskastl/traef

    As usual, #Ansible does the heavy lifting and deploys everything in the cluster.

    Have a lot of fun.

    #k8s #Kubernetes #Traefik #Ingress #GatewayAPI #DevOps #vagrant #libvirt #Nginx #HellYeah

  16. @dragotin @darix @OpenCloud @opensuse

    Here is the vagrant-libvirt setup I currently use to test the new package:
    codeberg.org/johanneskastl/ope
    github.com/johanneskastl/openc

    Most boilerplate and surrounding things are fine, the executable runs, but currently the setup is broken due to missing assets / assets not being created.

    As stated in the README, work in progress under heavy development... :-)

    #openSUSE #OpenCloud #Ansible #vagrant #libvirt #hellyeah #packagerslife

  17. Aaaaand another one:

    I played around with @Tronde's #OpenCloud #Ansible collection.

    Easy to use, feature-rich and very nice in general. Get up and running with a OpenCloud container via Podman in a matter of minutes.

    Here is a vagrant-libvirt setup using that Ansible collection:

    codeberg.org/johanneskastl/ope
    github.com/johanneskastl/openc

    (Actually, it is using a fork that contains some fixes, links to the pull requests are in the README).

    Have a lot of fun!

    #OpenCloud #vagrant #libvirt #Ansible #container #Podman #quadlets #hellyeah

  18. New treat incoming: I played around with #Podman and #Nginx as a #ReverseProxy. And as usual I ended up creating a new vagrant-libvirt setup...

    codeberg.org/johanneskastl/ngi
    github.com/johanneskastl/nginx

    One container running as a server (with a very valuable index.html...) and another container as reverse proxy.

    Two branches, one with quadlets (where everything worked out of the box) and another running "normal" containers.

    #DevOps #Nginx #Ansible #vagrant #libvirt #podman #containers #hellyeah