https://github.com/electrocucaracha/vagrant-boxes
Builds vagrant boxes for validating internal projects
https://github.com/electrocucaracha/vagrant-boxes
libvirt packer ubuntu virtualbox
Last synced: 29 days ago
JSON representation
Builds vagrant boxes for validating internal projects
- Host: GitHub
- URL: https://github.com/electrocucaracha/vagrant-boxes
- Owner: electrocucaracha
- Created: 2026-04-27T01:02:11.000Z (2 months ago)
- Default Branch: main
- Last Pushed: 2026-05-22T02:50:37.000Z (about 1 month ago)
- Last Synced: 2026-05-22T11:56:41.215Z (about 1 month ago)
- Topics: libvirt, packer, ubuntu, virtualbox
- Language: Shell
- Homepage: https://electrocucaracha.github.io/vagrant-boxes/
- Size: 177 KB
- Stars: 1
- Watchers: 0
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
Awesome Lists containing this project
README
# Vagrant boxes
[](https://opensource.org/licenses/Apache-2.0)
[](https://github.com/marketplace/actions/super-linter)

[](https://github.com/boyter/scc/)
[](https://github.com/boyter/scc/)
## Overview
This repository produces Ubuntu Vagrant base boxes
for the `libvirt`, `virtualbox`, and `utm` providers.
It focuses on a small, maintained set of Ubuntu releases:
- [Ubuntu 22.04](https://portal.cloud.hashicorp.com/vagrant/discover/electrocucaracha-boxes/ubuntu-jammy)
- [Ubuntu 24.04](https://portal.cloud.hashicorp.com/vagrant/discover/electrocucaracha-boxes/ubuntu-noble)
- [Ubuntu 26.04](https://portal.cloud.hashicorp.com/vagrant/discover/electrocucaracha-boxes/ubuntu-resolute)
## Benefits
- **Repeatable builds**:
the same templates and provisioning flow can be used every time a box is rebuilt.
- **Provider-ready artifacts**:
published outputs include `.box` files, checksums, and Vagrant `metadata.json`.
- **Consistent guests**:
the boxes apply the same user, networking, cleanup,
and packaging behavior across providers.
- **Smaller maintenance surface**:
the project keeps a narrow distro and provider matrix
so the outputs stay easier to validate and publish.
- **Flexible distribution**:
artifacts can be consumed from local `file://` metadata
or a hosted base URL.