I had time to update my old #Teleport #vagrant setup to work with the current @opensuse packages maintained by yours truly.
https://codeberg.org/johanneskastl/teleport_with_vagrant_libvirt
Also some roles were cleaned up, tested and are now fully compliant to #AnsibleLint...
Here you are: Vagrant-Setup with Ansible deploying k3s and GitLab inside k3s.
https://codeberg.org/johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible
https://github.com/johanneskastl/gitlab_on_k3s_vagrant_libvirt_ansible
Currently without the Runner, that comes next.
@jwolynko When it comes to on-prem, GitLab still seems to be the preferred solution (GitHub enterprise seems to be deprecated, thank the universe for that). I personally am running Forgejo wherever possible.
But most of the customers I know do run some form of GitLab. And I wanted to make sure I had a working test setup, whenever I need one. Currently I wanted to do some testing for GitLab runners on Kubernetes.
The package based ones are pretty simple to setup (not talking about maintenance, of course).
https://codeberg.org/johanneskastl/gitlab_vagrant_libvirt_ansible
https://codeberg.org/johanneskastl/gitlab_and_runner_vagrant_libvirt_ansible
Here is a small Docker CLI plugin I did, that launches a Vagrant-managed VM using Parallels on macOS and sets up a Docker context for it. Useful if you want a lightweight, no-surprises alternative to Docker Desktop — works on Intel & ARM, with binfmt for cross-arch builds.
"docker vagrant up" and you're ready to go.
Uuuuuuuh, #OpenBao (the open source fork of #Hashicorp #Vault) just released version 2.2.0 and now includes the UI, that was missing so far.
The package for @opensuse was adapted, tested and worked out fine. Will soon be available in #Tumbleweed!
If you want to test this out, feel free to use this vagrant-libvirt setup of mine:
https://codeberg.org/johanneskastl/openbao_vagrant_libvirt_ansible
I just added a #TalosLinux 1.9.3 (#Talos) #Vagrant box to the #ARM64 collection. This allows you to run Talos on your #AppleSilicon #MacBook. This is control-plane only, but you can patch the manifest to also run workloads.
You can find it right here:
Image: https://portal.cloud.hashicorp.com/vagrant/discover/gyptazy/talos1.9.3-arm64
Config: https://cdn.gyptazy.com/files/os/talos/vagrant/
All #ARM64 boxes: https://gyptazy.com/vagrant-images-for-apple-silicon-m1-m2/
« Je n'ai pas réussi à installer WSL2 sous Windows dans un Virtualbox lancé sous Fedora »
https://notes.sklein.xyz/2025-02-05_1628/zen/
#Virtualbox #Vagrant #WSL #needhelp
Si quelqu'un a une solution à mon problème, je suis preneur 
Another new position on my team (although, I think this one is really my-team adjacent. Really kinda depends on how you split things up but in any case, I can answer some questions about it). #fedihire
Details at https://jobs.lever.co/perforce/e242d65f-35c1-4c6b-a745-78e2f6a94326
Position Summary:
The Director of Product Development at Perforce is searching for a Enterprise Architect (#Linux System Solutions) to join the team. We are looking for an individual who loves Linux, views technology as a lifestyle, and has a passion for open source software. In this position, you’ll get hands on experience building, validating and publishing packages, and deploying Enterprise Linux distributions, and you’ll contribute to our most strategic product offerings.
At OpenLogic we do open source right, and our people make it happen. We provide the technical expertise required for maintaining healthy implementations of hundreds of integrated open source software packages. If your skills meet any of the specs below, now is the time to apply to be a part of our passionate team.
Responsibilities:
Troubleshoot and conduct root cause analysis on Enterprise Linux systems operated by third-party clients. Assisting them in resolving complex issues in mission critical environments.
Design, build, validate, package, and publish packages and images for world class Enterprise Linux distributions
Evaluate existing Enterprise Linux systems operated by third-party clients and identify areas for improvement.
Administer automation for provisioning and updating product distributions repositories.
Requirements:
BS or MS in Computer Science or equivalent
Strong command of Linux concepts, commands, and principles with experience managing OS installs, updates, upgrades, and migrations
Demonstrable experience designing or testing disaster recovery plans, including backup and recovery
Must have a firm understanding of the Enterprise Linux landscape, including the hierarchy of upstream/downstream repositories and communities, as well as an appreciation for the turmoil and turf wars that have transpired over the past few years
Must understand the unique use cases and requirements for platform specific deployments, including on-premises vs cloud vs hybrid, as well as bare metal vs virtualization
Demonstrable experience in one or more cloud-based technologies (AWS or Azure preferred)
Experience with virtualization (#Vagrant, #VirtualBox, #libvirt, #kvm, #qemu, etc) and containerization (#Docker, #Podman, etc), both small- and large-scale
Experience creating architectural blueprints and best practices for Linux systems
Ability to describe the purpose of CVSS scoring and relationship among various sources (e.g. NVD, Mitre, Red Hat)
Solid hands-on C programming knowledge with special attention on experience reproducing issues, conducting code/style reviews, and validating patches
Strong #bash shell and #Python (2 and 3) scripting knowledge and experience
In depth experience in systems and networking engineering / administration (preference to those with good understanding of troubleshooting issues down to Layer 2)
Experience with Linux #kernel development
Experience compiling software and building images with open-source tool chains (rpmbuild, mock, koji, kickstart, packer, etc)
Experience security hardening Linux systems and containers (openscap, PCI-DSS, CIS, STIGs, etc)
Experience with Git-based version control
Be flexible and willing to support occasional after-hours and weekend work
Experience working with a geographically dispersed virtual team
Preference given to candidates with implementation and troubleshooting experience on other broadly adopted open source technologies and CNCF technologies (e.g. #Kubernetes, Kafka, Nifi, Elasticsearch, Vault, InfluxDB, Keycloak, ActiveMQ, Redis, Tomcat, RHEL/CentOS/Rocky/Alma/Debian/SLES, Docker/Podman, etc.)
Preference given to candidates with experience in DevOps automation tools like #Jenkins, #Ansible, Terraform, Nexus/Artifactory, GitLab/#GitHub
#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
I have been playing around with Mercurial in the last couple of days, after digging into Subversion and JJ (aka Jujutsu) before that.
In case you want to start playing around with Mercurial, I put together a vagrant-libvirt setup (as is my usual routine) using Ansible. This includes hosting the repositories via Lighttpd or Apache, the latter in two flavors (CGI and WSGI). The setup prepares some repos and some local users, so you can also clone and push using SSH.
https://github.com/johanneskastl/mercurial_vagrant_libvirt_ansible
https://codeberg.org/johanneskastl/mercurial_vagrant_libvirt_ansible
Have a lot of fun!
I found the #bundlewrap config management system this week and had an itch to try it out.
https://docs.bundlewrap.org/guide/quickstart/
To play around with it more easily (and check the package I made for @openSUSE) I created a #vagrant setup (using vagrant-libvirt as usual):
https://github.com/johanneskastl/bundlewrap_vagrant_libvirt_ansible
This sets up a #Tumbleweed VM and prepares everything the vagrant user needs inside the VM so you can just log in and start playing with bundlewrap. Have a lot of fun...
Solución al error VirtualBox can’t operate in VMX root mode
Tras la actualización en Debian Trixie a la versión 6.12.6 del kernel de Linux he ido a arrancar mis máquinas virtuales de Virtualbox, y Vagrant me ha devuelto el siguiente error:
VBoxManage: error: VirtualBox can't operate in VMX root mode. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_VMX_IN_VMX_ROOT_MODE)
La extensión KVM del kernel es la que conecta con el sistema de virtualización de Intel, el que usa mi Thinkpad. En un primer momento he intentado desactivar en la BIOS el sistema de virtualización de Intel y reconfigurar el kernel. Eso no ha funcionado, Virtualbox necesita el sistema de virtualización para funcionar.
Luego he probado a desactivar los módulos KVM del kernel:
sudo modprobe -r kvm_intelsudo modprobe -r kvm
Tras la desactivación, Virtualbox vuelve a funcionar perfectamente.
En el caso de un procesador AMD, en lugar de Intel, los módulos a desactivar son los siguientes:
sudo modprobe -r kvm_amdsudo modprobe -r kvm
Actualización 19 marzo 2025
Con la actualización de virtualbox a la versión 7.0.20 en Debian, el responsable del paquete notifica lo siguiente:
In kernel 6.12, KVM initializes virtualization on module loading by default.
This prevents VirtualBox VMs from starting. In order to avoid this, either add
“kvm.enable_virt_at_load=0” parameter into kernel command line or unload
the corresponding kvm_XXX module.
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:
https://github.com/johanneskastl/subversion_vagrant_libvirt_ansible
As I am on a reading spree, #Mercurial will be next. And no, before you ask, I will not get into CVS after that...
I had to lose a couple hours of work to discover why no one uses #vagrant anymore
Ich habe ein Problem mit vagrant und frage mich, ob ich die einzige Person bin, die das macht obwohl es für mich ein normales Szenario ist. Anscheinend macht das niemand. Das Problem existiert im Internet nicht
Ich erstelle mit vagrant mehrere VMs und provisioniere sie mit ansible. Natürlich muss auch ansible-galaxy 1x ausgeführt werden. Aber das führt vagrant pro VM aus. Es läuft also 3x, gleichzeitig und kommt sich gegenseitig in die quere was die provisionierung crasht
Oh man, #Vagrant is already working better than it did the first time I tried this. 
Fedora 40 to 41 Upgrade
I bit the bullet this week and updated my laptop from Fedora 40 - 41. Outside of needing to reinstall goodhosts for VVV to work, the update is flawless.
I continue to be happy with my switch from macOS to Fedora and have even repurposed my Mac Studio to a media center PC on the TV in my office. It rips discs and displays content for me when I don't want
https://curtismchale.ca/2024/11/16/fedora-40-to-41-upgrade/
#LinksOfInterest #fedora #Framework #macos #vagrant
I don't know why I'm forever surprised at how bad - nearly unusable - Vmware Fusion is. This nonsense is getting uninstalled for good.
It's slow, the audio always sputters, the keyboards never work correctly, and integration with Vagrant is flaky at best.
Parallels, on the other hand is extortionately priced but at least it just works.
