home.social

#vagrant — Public Fediverse posts

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

  1. 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

  2. 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

  3. 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

  4. 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

  5. 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

  6. In in the last two week I tried to get the vagrant-libvirt setup for #Artifactory up and running.

    I now have a kind-of-working setup:
    codeberg.org/johanneskastl/art
    github.com/johanneskastl/artif

    This #vagrant setup creates a VM and installs the official Artifactory OSS version. It works kind of well in my tests. However, I deem the official systemd unit broken by design (separate toot following). So this setup installs a new unit that worked better in my tests (but not perfect, which I think is caused by the official startup scripts).

    Have fun!

    #DevOps #Artifactory #vagrant #libvirt #Ansible

  7. The #okd project has released a version of #microshift based on OKD, so of course I had to try it out.

    For those not familiar with it, OKD is a kubernetes distribution and is the "upstream" of RedHat's OpenShift.

    Here is a single-VM vagrant-libvirt setup that installs, configures and starts the Kubernetes cluster using #Ansible.

    codeberg.org/johanneskastl/mic
    github.com/johanneskastl/micro

    Have a lot of fun!

    #k8s #Kubernetes #Ansible #vagrant #libvirt #okd #microshift #microOKD #DevOps

  8. The #okd project has released a version of #microshift based on OKD, so of course I had to try it out.

    For those not familiar with it, OKD is a kubernetes distribution and is the "upstream" of RedHat's OpenShift.

    Here is a single-VM vagrant-libvirt setup that installs, configures and starts the Kubernetes cluster using #Ansible.

    codeberg.org/johanneskastl/mic
    github.com/johanneskastl/micro

    Have a lot of fun!

    #k8s #Kubernetes #Ansible #vagrant #libvirt #okd #microshift #microOKD #DevOps

  9. The #okd project has released a version of #microshift based on OKD, so of course I had to try it out.

    For those not familiar with it, OKD is a kubernetes distribution and is the "upstream" of RedHat's OpenShift.

    Here is a single-VM vagrant-libvirt setup that installs, configures and starts the Kubernetes cluster using #Ansible.

    codeberg.org/johanneskastl/mic
    github.com/johanneskastl/micro

    Have a lot of fun!

    #k8s #Kubernetes #Ansible #vagrant #libvirt #okd #microshift #microOKD #DevOps

  10. The #okd project has released a version of #microshift based on OKD, so of course I had to try it out.

    For those not familiar with it, OKD is a kubernetes distribution and is the "upstream" of RedHat's OpenShift.

    Here is a single-VM vagrant-libvirt setup that installs, configures and starts the Kubernetes cluster using #Ansible.

    codeberg.org/johanneskastl/mic
    github.com/johanneskastl/micro

    Have a lot of fun!

    #k8s #Kubernetes #Ansible #vagrant #libvirt #okd #microshift #microOKD #DevOps

  11. The #okd project has released a version of #microshift based on OKD, so of course I had to try it out.

    For those not familiar with it, OKD is a kubernetes distribution and is the "upstream" of RedHat's OpenShift.

    Here is a single-VM vagrant-libvirt setup that installs, configures and starts the Kubernetes cluster using #Ansible.

    codeberg.org/johanneskastl/mic
    github.com/johanneskastl/micro

    Have a lot of fun!

    #k8s #Kubernetes #Ansible #vagrant #libvirt #okd #microshift #microOKD #DevOps

  12. I found Squest (github.com/HewlettPackard/sque) recently, which is a self-service portal built on top of #AWX #RedHat #AAP (Ansible Automation Platform). Of course I had to try this out...

    @christianhuth put together a Helm chart, while I tried to get upstream's way of deploying to work (they are using an #Ansible playbook-role construct to install this into #Kubernetes).

    Here is the first result, the helm-based #vagrant #libvirt setup:
    codeberg.org/johanneskastl/squ
    github.com/johanneskastl/sques

    (The ansible branch using upstream's deployment will follow, once I get it working with vagrant-libvirt...)

    Have a lot of fun!

    #DevOps #k8s #selfserviceportal #squest #hellyeah

  13. ....aaaaaand #OpenBao (the fork of #Hashicorp #Vault) is on its way to @opensuse #Tumbleweed in the latest version 2.2.1. Since 2.2.0 the webui is included in OpenBao, so this can be a full replacement for Vault!

    Looking forward to doing more testing with it!

    In case you want to try it out, here is a #vagrant #libvirt setup using #Ansible to prepare an OpenBao server VM and a client using a secret.
    codeberg.org/johanneskastl/ope

    #secretmanagement #kms #devops

  14. #FediBrain moving to libvirt but still using Vagrant - only vagrant 2.4.0-1 seems to work for me - Older versions cannot download boxes, newer versions doesn't recognize libvirt. What the f... did I do wrong or is it just a mess?
    #libvirt #vagrant #version #WhatAMess

  15. #FediBrain moving to libvirt but still using Vagrant - only vagrant 2.4.0-1 seems to work for me - Older versions cannot download boxes, newer versions doesn't recognize libvirt. What the f... did I do wrong or is it just a mess?
    #libvirt #vagrant #version #WhatAMess

  16. #FediBrain moving to libvirt but still using Vagrant - only vagrant 2.4.0-1 seems to work for me - Older versions cannot download boxes, newer versions doesn't recognize libvirt. What the f... did I do wrong or is it just a mess?
    #libvirt #vagrant #version #WhatAMess

  17. #FediBrain moving to libvirt but still using Vagrant - only vagrant 2.4.0-1 seems to work for me - Older versions cannot download boxes, newer versions doesn't recognize libvirt. What the f... did I do wrong or is it just a mess?
    #libvirt #vagrant #version #WhatAMess

  18. As one does between the years, I have started digging into #subversion (the version control system) to learn more about its concepts. Because, why not? At least it helps me to be grateful for the ease of use I have with #git (sorry subversion...).

    In case you want to have a look, I built a #vagrant setup to easily play around with Subversion:

    github.com/johanneskastl/subve

    As I am on a reading spree, #Mercurial will be next. And no, before you ask, I will not get into CVS after that...

    #svn #vcs #versioncontrol #softwarearcheology #oldiesbutgoldies

  19. CW: debian/docker project show-and-tell with a lot of links

    One of my most useful personal projects is my own customized #Debian #Linux ISO image, with my packages, tools, dotfiles and configuration just the way I want it.

    It uses Debian Live to build the ISO, which can be used as a #liveusb or an installer. I can build it locally via #vagrant with #libvirt, or using a #GitHub workflow.

    Here's what I think is one of the coolest things: the GitHub workflow builds the ISO then packages it into a #Docker image. When run, that container provides the following:

    • an HTTP server from which the ISO can be download
    • a #VNC server (using #novnc and #Xvfb) for connecting to the live instance running on #QEMU with #kvm
    • a #websockify interface for accessing the VNC server in a web browser

    It's so useful for me to have my environment with me wherever I go as I carry it around with me on my #Ventoy thumb drive, whether running it as a one-off live instance or the installer, and to have the environment in a Docker container where I can spin it up as needed.

  20. CW: debian/docker project show-and-tell with a lot of links

    One of my most useful personal projects is my own customized #Debian #Linux ISO image, with my packages, tools, dotfiles and configuration just the way I want it.

    It uses Debian Live to build the ISO, which can be used as a #liveusb or an installer. I can build it locally via #vagrant with #libvirt, or using a #GitHub workflow.

    Here's what I think is one of the coolest things: the GitHub workflow builds the ISO then packages it into a #Docker image. When run, that container provides the following:

    • an HTTP server from which the ISO can be download
    • a #VNC server (using #novnc and #Xvfb) for connecting to the live instance running on #QEMU with #kvm
    • a #websockify interface for accessing the VNC server in a web browser

    It's so useful for me to have my environment with me wherever I go as I carry it around with me on my #Ventoy thumb drive, whether running it as a one-off live instance or the installer, and to have the environment in a Docker container where I can spin it up as needed.

  21. CW: debian/docker project show-and-tell with a lot of links

    One of my most useful personal projects is my own customized #Debian #Linux ISO image, with my packages, tools, dotfiles and configuration just the way I want it.

    It uses Debian Live to build the ISO, which can be used as a #liveusb or an installer. I can build it locally via #vagrant with #libvirt, or using a #GitHub workflow.

    Here's what I think is one of the coolest things: the GitHub workflow builds the ISO then packages it into a #Docker image. When run, that container provides the following:

    • an HTTP server from which the ISO can be download
    • a #VNC server (using #novnc and #Xvfb) for connecting to the live instance running on #QEMU with #kvm
    • a #websockify interface for accessing the VNC server in a web browser

    It's so useful for me to have my environment with me wherever I go as I carry it around with me on my #Ventoy thumb drive, whether running it as a one-off live instance or the installer, and to have the environment in a Docker container where I can spin it up as needed.

  22. CW: debian/docker project show-and-tell with a lot of links

    One of my most useful personal projects is my own customized #Debian #Linux ISO image, with my packages, tools, dotfiles and configuration just the way I want it.

    It uses Debian Live to build the ISO, which can be used as a #liveusb or an installer. I can build it locally via #vagrant with #libvirt, or using a #GitHub workflow.

    Here's what I think is one of the coolest things: the GitHub workflow builds the ISO then packages it into a #Docker image. When run, that container provides the following:

    • an HTTP server from which the ISO can be download
    • a #VNC server (using #novnc and #Xvfb) for connecting to the live instance running on #QEMU with #kvm
    • a #websockify interface for accessing the VNC server in a web browser

    It's so useful for me to have my environment with me wherever I go as I carry it around with me on my #Ventoy thumb drive, whether running it as a one-off live instance or the installer, and to have the environment in a Docker container where I can spin it up as needed.