Chapter 8. Disconnected installation


You can install containerized Ansible Automation Platform in an environment that does not have an active internet connection. To do this you need to obtain and configure the RPM source dependencies before performing the disconnected installation.

The Ansible Automation Platform containerized setup bundle installation program does not include RPM source dependencies from the BaseOS and AppStream repositories. It relies on the host system’s package manager to resolve these dependencies.

To access these dependencies in a disconnected environment, you can use one of the following methods:

  • Use Red Hat Satellite to synchronize repositories in your disconnected environment.
  • Use a local repository that you create with the reposync command on a Red Hat Enterprise Linux host that has an active internet connection.
  • Use a local repository that you create from a mounted Red Hat Enterprise Linux Binary DVD ISO image.

With the reposync command you can to synchronize the BaseOS and AppStream repositories to a local directory on a Red Hat Enterprise Linux host with an active internet connection. You can then transfer the repositories to your disconnected environment.

Prerequisites

  • A Red Hat Enterprise Linux host with an active internet connection.

Procedure

  1. Attach the BaseOS and AppStream repositories using subscription-manager, replacing <RHEL_VERSION> with your RHEL version number:

    $ sudo subscription-manager repos \
        --enable rhel-<RHEL_VERSION>-baseos-rhui-rpms \
        --enable rhel-<RHEL_VERSION>-appstream-rhui-rpms
  2. Install the yum-utils package:

    $ sudo dnf install yum-utils
  3. Synchronize the repositories with the reposync command. Replace <path_to_download> with a suitable value.

    $ sudo reposync -m --download-metadata --gpgcheck \
        -p <path_to_download>

    For example:

    $ sudo reposync -m --download-metadata --gpgcheck \
        -p rhel-repos
    • Use reposync with the --download-metadata option and without the --newest-only option for optimal download time.
  4. After the reposync operation is complete, compress the directory:

    $ tar czvf rhel-repos.tar.gz rhel-repos
  5. Move the compressed archive to your disconnected environment.
  6. On the disconnected environment, create a directory to store the repository files:

    $ sudo mkdir /opt/rhel-repos
  7. Extract the archive into the /opt/rhel-repos directory. The following command assumes the archive file is in your home directory:

    $ sudo tar xzvf ~/rhel-repos.tar.gz -C /opt
  8. Create a Yum repository file at /etc/yum.repos.d/rhel.repo with the following content, replacing <RHEL_VERSION> with your RHEL version number:

    [RHEL-BaseOS]
    name=Red Hat Enterprise Linux BaseOS
    baseurl=file:///opt/rhel-repos/rhel-<RHEL_VERSION>-baseos-rhui-rpms
    enabled=1
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
    
    [RHEL-AppStream]
    name=Red Hat Enterprise Linux AppStream
    baseurl=file:///opt/rhel-repos/rhel-<RHEL_VERSION>-appstream-rhui-rpms
    enabled=1
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
  9. Import the gpg key to allow the system to verify the packages, replacing <RHEL_VERSION> with your RHEL version number:

    $ sudo rpm --import /opt/rhel-repos/rhel-<RHEL_VERSION>-baseos-rhui-rpms/RPM-GPG-KEY-redhat-release
  10. Verify the repository configuration:

    $ sudo yum repolist

You can use a Red Hat Enterprise Linux Binary DVD image to access the necessary RPM source dependencies in a disconnected environment.

Prerequisites

Procedure

  1. In your disconnected environment, create a mount point directory to serve as the location for the ISO file:

    $ sudo mkdir /media/rhel
  2. Mount the ISO image to the mount point. Replace <version_number> and <arch_name> with suitable values:

    $ sudo mount -o loop rhel-<version_number>-<arch_name>-dvd.iso /media/rhel
    • Note: The ISO is mounted in a read-only state.
  3. Create a Yum repository file at /etc/yum.repos.d/rhel.repo with the following content:

    [RHEL-BaseOS]
    name=Red Hat Enterprise Linux BaseOS
    baseurl=file:///media/rhel/BaseOS
    enabled=1
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
    
    [RHEL-AppStream]
    name=Red Hat Enterprise Linux AppStream
    baseurl=file:///media/rhel/AppStream
    enabled=1
    gpgcheck=1
    gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
  4. Import the gpg key to allow the system to verify the packages:

    $ sudo rpm --import /media/rhel/RPM-GPG-KEY-redhat-release
  5. Verify the repository configuration:

    $ sudo yum repolist

8.2. Performing a disconnected installation

A disconnected installation installs containerized Ansible Automation Platform without requiring network access to external registries.

Prerequisites

Procedure

  1. Log in to the Red Hat Enterprise Linux host as your non-root user.
  2. Update the inventory file by following the steps in Configuring the inventory file.

    Note

    Do not include registry_username or registry_password in your inventory file for disconnected installations. These variables are only required for online installations. All container images are pre-packaged in the setup bundle.

  3. Ensure you include the following variables in your inventory file under the [all:vars] group:

    bundle_install=true
    # The bundle directory must include /bundle in the path
    bundle_dir='{{ lookup("ansible.builtin.env", "PWD") }}/bundle'
  4. Follow the steps in Installing containerized Ansible Automation Platform to install containerized Ansible Automation Platform and verify your installation.
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

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.

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 Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top