wikitops / ansible_buildah

Ansible playbook to deploy buildah on Linux Vagrant instance.

Ansible : Playbook Buildah

The aim of this project is to deploy Buildah on a Vagrant instance.

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.

Prerequisites

What things you need to run this Ansible playbook :

• Vagrant must be installed on your computer
• Update the Vagrant file based on your computer (CPU, memory), if needed
• Update the operating system to deploy in the Vagrant file (default: CentOS 8)

Usage

A good point with Vagrant is that you can create, update and destroy all architecture easily with some commands.

Be aware that you need to be in the Vagrant directory to be able to run the commands.

Deployment

To deploy Buildah on a Vagrant instance, just run this command :

$ vagrant up

If everything run as expected, you should be able to list the virtual machine created :

$ vagrant status

Current machine states:

buildah01                   running (virtualbox)

If everything run as expected, you should have a running instance of Buildah on the Vagrant node.

Destroy

To destroy the Vagrant resources created, just run this command :

$ vagrant destroy

How-To

This section list some simple command to use and manage the playbook and the Vagrant hosts.

Update with Ansible

To update the Buildah instance configuration with Ansible, you just have to run the Ansible playbook buildah.yml with this command :

$ ansible-playbook buildah.yml

Update with Vagrant

To update the Buildah instance configuration with Vagrant, you just have to run provisioning part of the Vagrant file :

$ vagrant provision

Connect to Vagrant instance

To be able to connect to a Vagrant instance, you should use the CLI which is configured to automatically use the default SSH key :

$ vagrant ssh buildah01

Author

Member of Wikitops : https://www.wikitops.io/

Licence

This project is licensed under the MIT License. For the full text of the license, see the LICENSE file.