About image registries

An image registry is an online service that stores Docker images. Docker images are either images that you build yourself, or images from third parties that you want to consume, for example, a base image of Node.js or a base image of Java. The image registry is also the place where Kubernetes and OpenShift download from when they deploy the application for ongoing development or testing within each of those environments.

Some registries are protected and limit access to authenticated users only. You might use one or multiple image registries each having different credentials. In the following section we’ll discuss when you’ll need a registry configured within Codewind, and how to store your credentials for use when the registry has been secured.

When you need to define an image registry

You need to enter configuration details for the image registry for any of the following conditions:

  • Building a project with a Dockerfile that pulls from a protected image registry that requires authentication.
  • Working with Appsody projects that pull stack images from a protected image registry that requires authentication.
  • When you are using Codewind remotely
  • When you are using Che to build Codewind style projects

When you add an image registry, Codewind logs you into the image registry on your local machine as if you had locally run docker login.

Adding your first image registry entry to Codewind

Adding an image registry and connection details is done using your IDE (local/remote) or by way of the Che IDE when running in Che.

After your IDE is started and running, add the image registry to be used with Codewind.

  1. From your IDE, open the window for adding your image registry.
    • In Eclipse: Right-click a remote connection in the Codewind Explorer view and select Manage Image Registries.
    • In VS Code: Right-click a remote connection and select Image Registry Manager or use the Image Registry Manager command on the command palette.
  2. Then, follow the prompts and fill out the required information to add your image registry. For recommended values for common registries, see the examples.
    • Registry server name, domain name, or address: <registry-to-push-or-pull-images-to>
    • User name: <Your user name>
    • Password or API key: <Your password or API key>
    • Also enter a namespace if you want to use the registry as the push registry.

Codewind container registry guidance

When you run Codewind on Kubernetes for Codewind style projects, Codewind uses buildah to build container images from Dockerfiles and to push the images to an image registry that you specify. Use the Image Registry Manager in your Codewind IDE to configure the registry to use.

Use any registry as long as buildah and the node that Codewind is running on can resolve the registry hostname. If buildah cannot resolve the registry hostname, buildah cannot push your projects to the registry, and deployment on Kubernetes is prevented.


These examples show recommended values for common registries. The following image registries are tested and verified with Codewind:

  • Docker Hub:
    • Address: docker.io
    • Namespace: <namespace>
    • Credentials: Docker Hub user name and password or access token
    • Note: For Docker Hub, the Namespace value is likely to be your user name.
  • Quay.io:
    • Address: https://quay.io
    • Namespace: <namespace>
    • Credentials: Quay.io user name and encrypted password
  • Artifactory
    • Address: <artifactory-hostname>
    • Namespace: <namespace>
    • Credentials: Artifactory user name and access token
  • OpenShift Registry
    • Address: docker-registry.default.svc:5000
    • Namespace: <project>
    • Credentials: OpenShift user name and access token

Adding registries to OKD and OpenShift

To use the OpenShift internal container registry with Codewind, see Adding the OpenShift internal registry with Codewind.

Next step: Continue to instructions for Creating and importing projects.