Building and Installing the MicroShift Containers

Building and installing the MicroShift and MicroShift AIO containers for local development

Building the MicroShift Containers

Install podman if not yet installed:

sudo dnf install -y podman

Clone the repository and cd into it:

git clone
cd microshift

Build the MicroShift image:

make microshift

Build the MicroShift bundled (All-In-One) image:

make microshift-aio

Tagging the Image

After building the MicroShift image, the podman tag command can be used to modify the image name to suit your needs. See the example below.

IMAGE=$(podman images | grep micro | awk '{print $3}')
podman tag ${IMAGE}

Running the MicroShift Containers

Depending on which image version you built, follow the documentation to run the image.

Follow Getting Started with MicroShift Containerized
Substitute the image name:tag in the systemd unit file at /etc/system/systemd/microshift.service with the newly built image name:tag.

Follow Using MicroShift for Application Development
Substitute the image name:tag in the podman command with the newly built image name:tag.

Building offline container image rpms

packaging/rpm/ is responsible for extracting the right MicroShift component container images into an rpm, srpm, or triggering a build in copr. queries the MicroShift code via pkg/release/ to identify the MicroShift component images for the release in each architecture, it accepts one parameter with the desired action (rpm, srpm, copr), being rpm the default.

For example:

cd packaging/rpm


cd packaging/rpm
export COPR_REPO=@redhat-et/microshift-containers
./ copr

Please note that @redhat-et/microshift-containers is the default, being @redhat-et a group in copr, for a regular user you can user username/microshift-containers for example.

Last modified May 24, 2022 at 4:02 PM PST : typo do -> to (#168) (77030fc)
Last modified May 24, 2022 at 4:02 PM PST : typo do -> to (#168) (77030fc)