GitLab is a complete DevOps platform, delivered as a single application. This makes GitLab unique and makes Concurrent DevOps possible, unlocking your organization from the constraints of a pieced together toolchain. Join us for a live Q&A to learn how GitLab can give you unmatched visibility and higher levels of efficiency in a single application across the DevOps lifecycle.
Learn more about GitLab: https://about.gitlab.com/
- Packaging with Packer
- Minimal Vagrant base box implementation
- Support QEMU Guest Agent
- Support VirtualBox Guest Additions
- Support Vagrant synced folder with rsync
- Support Vagrant provisioner with Ansible
- Standardize disk partition with GPT
- Standardize file system mount with UUID
- Standardize network interface with
eth0
Once you have Vagrant and VirtaulBox installed, run the following commands under your project directory:
# Initialize Vagrant
vagrant init alvistack/gitlab-runner-15.4
# Start the virtual machine
vagrant up
# SSH into this machine
vagrant ssh
# Terminate the virtual machine
vagrant destroy --force
You could also run our Molecule test cases if you have Vagrant and Libvirt installed, e.g.
# Run Molecule on GitLab Runner 15.4
molecule converge -s gitlab-runner-15.4-libvirt
Please refer to .gitlab-ci.yml for more information on running Molecule.
Release tags could be find from GitHub Release of this repository. Thus using these tags will ensure you are running the most up to date stable version of this image.
Version tags ended with .0.0 are rolling release rebuild by GitLab pipeline in weekly basis. Thus using these tags will ensure you are running the latest packages provided by the base image project.
- Code released under Apache License 2.0
- Docs released under CC BY 4.0
- Wong Hoi Sing Edison