Connect an engine to an image registry

Connect an engine to an image registry for script execution.

Using an engine to communicate with an image registry streamlines deployment by managing dependencies, ensuring version control, and facilitating scalability, load balancing, and secure access to private images.

To use an engine, you need to connect the engine to an authenticated Docker image registry and then set it up in the tenant.

This procedure uses the --username and --password command line options to pass the username and password directly. For environments where command history or logs are visible to others, consider more secure methods like Docker configuration files for handling authentication in production or CI/CD environments. For more details, see docker login or podman-login.

1. Open a terminal on the machine where your engine is running.
2. Run docker login with username and password.

   docker login --username=<your-username> --password=<your-password> <registry-url>

   Replace <your-username>, <your-password>, and <registry-url> with your Docker registry credentials and the URL of your Docker image registry.
3. (Optional) Search for or pull a Docker image.

   After logging in successfully, you can optionally validate access to images by searching for an image or pulling an image from the registry to your local machine using the docker search or docker pull command.

   docker search <registry-url>/<image-name>:<tag>
   docker pull <registry-url>/<image-name>:<tag>

   Replace <registry-url>, <image-name>, and <tag> with your registry URL, the name of the Docker image, and the image tag, respectively.
4. In the tenant, set up the engine to pull images from a private image registry.