How to push an image to your own container registry

Created by Steve Place, Modified on Sun, Feb 16 at 9:35 PM by Steve Place

If your company's network won't let you pull images from DockerHub or Stardog's JFrog repo, you can pull the image onto your local machine, tag it, and push it to your private container registry (where it will then be pulled from in your helm charts). This article walks through the steps to do that.

Step 1: Pulling an Image

To start, pull an image from the image from the source registry. For example, to pull the stardog image from DockerHub:

docker pull stardog/stardog

This command fetches the latest Stardog image from Docker Hub and stores it in your local Docker daemon.

Step 2: Tagging the Image

Before pushing the image to your private registry, you need to tag it with the appropriate registry URL and repository name. The syntax is:

docker tag <source-image>:<tag> <private-registry>/<repository>:<tag>

For example, if your private registry is hosted at myregistry.example.com and your repository is my-stardog, you would tag the image as follows:

docker tag stardog/stardog myregistry.example.com/my-stardog:1.0

Step 3: Logging into the Private Registry

If your registry requires authentication, log in using:

docker login <private-registry>

For example:

docker login myregistry.example.com

You will be prompted for your credentials.

Step 4: Pushing the Image to the Private Registry

Once logged in, push the image to your registry using:

docker push <private-registry>/<repository>:<tag>

For example:

docker push myregistry.example.com/my-stardog:1.0

This command uploads the image to your private registry, making it accessible for deployments.

Step 5: Verifying the Image in the Registry

To confirm that the image was pushed successfully, you can:

Check the web interface of your registry.
Use the registry API (if available) to list stored images.

Try pulling the image from another machine using:

docker pull myregistry.example.com/my-stardog:1.0