call
Go to Console

 

Container Registry Console Guide

 

This page provides a complete guide to the Container Registry section of the Namirasoft Container Registry Console. It explains what a registry connection is, why it matters, and the purpose of every field on the form, including the registry types you can connect and how to create the credential each one needs.

What Is a Registry Connection?

A registry connection is a saved link between Namirasoft and one container registry. Each connection has a name, records which type of registry it is, and points to the credential Namirasoft uses to authenticate. A container registry is the service that stores your container images, such as Amazon Elastic Container Registry.

 

Namirasoft Container Registry reaches the registry using a credential you saved in Namirasoft Credential, so authorized Namirasoft applications can connect. It does not store your container images, and your credentials are kept encrypted.

Why Secure Registry Access Matters

Teams keep images across many registries, and each one has its own sign in method and access keys. Copying those keys into every tool and sharing them across people is hard to track and easy to get wrong, which risks exposure or broken access. A single connection that references one managed credential keeps access consistent and under control.

Overview of Registry Fields and Options

These are the fields on the Container Registry form, including the ones Namirasoft sets automatically.

 

  • ID (String): This is the unique identifier Namirasoft Container Registry generates when you create a connection. You do not enter it, and it is used internally to track and reference the connection.

 

  • User ID (Namirasoft Account’s ID): This is the ID of the Namirasoft Account that created the connection. It links the connection to the person who owns it.

 

  • Workspace ID (Namirasoft Workspace’s ID): This is the Namirasoft Workspace the connection belongs to, which lets you organize connections by project, environment, or team.

 

  • Name (String): This is a label you choose to identify the connection, such as Production ECR or Team Harbor. It helps you recognize the connection and has no effect on how it signs in.

 

  • Type (Enum): This selects which container registry Namirasoft connects to. The form is the same for every type; only the credential differs. Choose the type that matches your registry:

    • Public Repository connects to a public registry that needs no sign in, for open source and public base images.
    • Amazon Elastic Container Registry is Amazon Web Services’ managed registry with IAM based access and image scanning.
    • Azure Container Registry is Microsoft Azure’s managed registry with role based access and geo replication.
    • Google Container Registry is Google Cloud’s original registry backed by Cloud Storage.
    • Google Artifact Registry is Google Cloud’s current registry for images and packages, and the successor to Container Registry.
    • Sonatype Nexus is a self hosted repository manager that also stores container images.
    • JFrog Artifactory is a self hosted repository that hosts container images and many other formats.
    • Harbor is an open source registry you host yourself, with policy based access and scanning.
    • GitHub Container Registry is the registry built into GitHub, served at ghcr.io.
    • GitLab Container Registry is the registry built into GitLab, one per project.
    • Private Registry connects to any registry that signs in with a username and password, such as Docker Hub.

 

  • Credential (Namirasoft Credential’s ID): This is the credential Namirasoft uses to sign in to the registry, which you save in Namirasoft Credential and select here. Its label changes to match your Type, for example GCP Credential ID. Your credential is kept encrypted. Public Repository needs no credential. Use the steps for your registry to create the right one:

 

Amazon Elastic Container Registry
  1. Sign in to the AWS IAM console and create an access key with permission to use Amazon ECR. See the full steps
  2. Copy the Access Key ID and Secret Access Key.
  3. In Namirasoft Credential, create an AWS credential with them, then select it here. How do I create it?

 

Azure Container Registry
  1. Sign in to the Azure portal, register an app in Microsoft Entra ID, and give it access to your registry.
  2. Copy the Tenant ID, Client ID, and a Client Password. Find the Tenant ID and Client ID, create a Client Password
  3. In Namirasoft Credential, create an Azure credential with them, then select it here. How do I create it?

 

Google Container Registry
  1. Sign in to the Google Cloud service accounts console and create a service account with access to the registry.
  2. Add a key to the service account and download it as a JSON file. See the full steps
  3. In Namirasoft Credential, create a GCP credential with the JSON file, then select it here. How do I create it?

 

Google Artifact Registry
  1. Sign in to the Google Cloud service accounts console and create a service account with access to the registry.
  2. Add a key to the service account and download it as a JSON file. See the full steps
  3. In Namirasoft Credential, create a GCP credential with the JSON file, then select it here. How do I create it?

 

Sonatype Nexus
  1. Sign in to your Nexus web console and open Security, then Users.
  2. Use or create a user with access to your Docker repository, and note its username and password.
  3. In Namirasoft Credential, create a Basic Auth credential with them, then select it here. How do I create it?

 

JFrog Artifactory
  1. Sign in to Artifactory and open your user profile.
  2. Generate an identity token, or use your username and password, with access to your Docker repository, and copy the values.
  3. In Namirasoft Credential, create a Basic Auth credential with them, then select it here. How do I create it?

 

Harbor
  1. Sign in to Harbor and open your project, then Robot Accounts.
  2. Create a robot account with pull and push access, and copy its name and secret. You can also use your account’s username and CLI secret from your user profile.
  3. In Namirasoft Credential, create a Basic Auth credential with them, then select it here. How do I create it?

 

GitHub Container Registry
  1. Sign in to GitHub and open Settings, Developer settings, Personal access tokens.
  2. Generate a classic token with the read:packages and write:packages scopes, and copy it.
  3. In Namirasoft Credential, create a GitHub credential with the token, then select it here. How do I create it?

 

GitLab Container Registry
  1. Sign in to GitLab and open Access Tokens in your user settings.
  2. Create a token with the read_registry and write_registry scopes, and copy it.
  3. In Namirasoft Credential, create a GitLab credential with the token, then select it here. How do I create it?

 

Private Registry
  1. Get the username and password for your registry. For Docker Hub, sign in and open Account Settings, Personal access tokens.
  2. Create an access token to use as the password, with your Docker ID as the username, and copy it.
  3. In Namirasoft Credential, create a Basic Auth credential with them, then select it here. How do I create it?

 

 

  • Description (String): This is an optional note explaining what the connection is for, such as Production images for the billing service. It has no effect on how the connection signs in.

 

  • Created At (DateTime): This is the date and time the connection was created. Namirasoft sets it automatically and you cannot change it.

 

  • Updated At (DateTime): This is the date and time the connection was last changed, which helps you track updates. Namirasoft sets it automatically.

Ready to Get Started or Want to Explore the Console Guide?

Get Started Explore Console Guide