rfairley

!!! Note: In process of reworking this - since modules are no longer being used for Rust packages, only an update to the RPM is necessary, but different from the usual workflow for RPM packages. Pending information from Fedora Rust folks on what the new processes without modules is.

Updating fedora-coreos-pinger

I run these steps from a fedora:rawhide container, with the RPM build tools installed inside the container.

To start and provision the container:

podman run --name=rust-dev-rawhide --privileged --net=host -v /path/to/working-directory:/srv/work -ti registry.fedoraproject.org/fedora:rawhide

rfairley

Testing ignition-dracut changes locally in Fedora CoreOS

1. Download the Ignition RPM source by cloning the following repository: https://src.fedoraproject.org/rpms/ignition

   git clone https://src.fedoraproject.org/rpms/ignition.git
   cd ignition
   

2. From the ignition-dracut repository you made commits in, push your ignition-dracut changes to your fork of the ignition-dracut repository (any branch is fine).

wpscholar

Typing vagrant from the command line will display a list of all available commands.

Be sure that you are in the same directory as the Vagrantfile when running these commands!

Creating a VM

• vagrant init -- Initialize Vagrant with a Vagrantfile and ./.vagrant directory, using no specified base image. Before you can do vagrant up, you'll need to specify a base image in the Vagrantfile.
• vagrant init <boxpath> -- Initialize Vagrant with a specific box. To find a box, go to the public Vagrant box catalog. When you find one you like, just replace it's name with boxpath. For example, vagrant init ubuntu/trusty64.

Starting a VM

• vagrant up -- starts vagrant environment (also provisions only on the FIRST vagrant up)