Search

Chapter 8. Creating a Podman site in a restricted environment

download PDF

In a production environment which has no or limited internet access, you might need to mirror the required images to create a site.

This procedure outlines how to use Podman and tar files for managing container images. If a registry is available in the restricted environment, the same process can be followed. Ensure that the environment variables are set to reference the images in the registry after they have been populated.

Prerequisites

  • A Linux machine with internet access to download the images.
  • A Linux machine in a restricted environment where you want to create the site.

This can be one machine, where the machine is moved to the restricted environment.

Procedure

  1. Log in to registry.redhat.io on the machine with internet access:

    $ podman login -u USERNAME -p PASSWORD registry.redhat.io
  2. Download the images required for a Podman site by creating a site:

    $ skupper init

    If you require a console, use the following command to ensure the extra images are downloaded

    $ skupper init --enable-console --enable-flow-collector

    After creating the site, the following images are listed using podman image ls -a:

    • registry.redhat.io/service-interconnect/skupper-router-rhel9
    • registry.redhat.io/service-interconnect/skupper-controller-podman-rhel9
    • registry.redhat.io/service-interconnect/skupper-flow-collector-rhel9 (console only)
    • registry.redhat.io/openshift4/ose-prometheus (console only)

    The tags are determined by the version of the skupper CLI.

  3. Create tar files for each image, for example:

    $ podman save -o skupper-controller.tar  registry.redhat.io/service-interconnect/skupper-controller-podman-rhel9:<tag>

    where <tag> is the tag shown from using the podman image ls -a command.

  4. Copy the tar files to the machine in the restricted environment.
  5. On the machine in the restricted environment, load the image from the tar files, for example:

    podman load -i skupper-controller.tar
  6. Change the image tags to remove reference to registry.redhat.io:

    podman tag registry.redhat.io/service-interconnect/skupper-router-rhel9:<tag> service-interconnect/skupper-router-rhel9:<tag>

    This step is required to avoid the machine attempting to pull images from registry.redhat.io.

  7. Configure the skupper CLI to use the mirrored images by setting the following environment variables:

    $ export SKUPPER_CONTROLLER_PODMAN_IMAGE=service-interconnect/skupper-controller-podman-rhel9:<tag>
    $ export QDROUTERD_IMAGE=service-interconnect/skupper-router-rhel9:<tag>

    If you require a console, you also require the following environment variables:

    $ export SKUPPER_FLOW_COLLECTOR_IMAGE=service-interconnect/skupper-flow-collector-rhel9:<tag>
    $ export PROMETHEUS_SERVER_IMAGE=openshift4/ose-prometheus:<tag>
  8. Create a site, for example:

    $ skupper init
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.