Documentation update To provide a better user experience, we have now created a separate documentation space for BMC Helix Automation Console (previously called BMC Helix Vulnerability Management). Users of BMC Helix Automation Console can find the latest documentation at BMC Helix Automation Console..

Troubleshooting issues related to Docker

You may encounter the following issues while installing and using Docker.

Error while creating a local Docker registry 

Before installing or upgrading to TrueSight Automation Console, you are required to create a local Docker registry to pull images. When you run the docker run -d \ command, you may get the following error:

Unable to find image 'registry:2' locally
docker: Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit.
See 'docker run --help'.

This error occurs because from November 2020, Docker has limited the number of Anonymous and Free Docker Hub users to 100 and 200 container image pull requests. 

Resolution

To prevent this error, choose either of the following options:

  • Use your registered Docker Hub credentials to create a local registry. Run the following command to log in to Docker.

    docker login
    Login with your Docker ID to push and pull images from Docker Hub. If you don't have a Docker ID, head over to https://hub.docker.com to create one.
    Username:<Enter a username>
    Password:<Enter a password>

    After successfully logging in, continue to create a local registry. For details, see Preparing-for-installation or Preparing-for-upgrade.

  • TrueSight Automation Console now provides a registry2.tar. Run the following command to load the registry image in your environment:

    docker load -i <TSAC-Image-Unzip-Location>/registry/registryv2.tar

      This loads the registry image using which you can create a local registry. For details, see Preparing-for-installation or Preparing-for-upgrade.

MCR installation fails with an error about the installed package 

Installation of Mirantis Container Runtime (MCR) fails on an RHEL 8 system with an error related to the installed package. This issue occurs because the existing runc package that comes with Podman conflicts with the MCR package. 

Resolution

On the RHEL 8 system, run the following command and then install MCR.

sudo yum remove runc

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*