Scaleway Elements Container Registry is a fully-managed mutualized container registry, designed to facilitate storing, managing and deploying container images. The service simplifies the development to production workflow as there is no need to operate an own container registry or to worry about the underlying infrastructure. A container image consists of several bundled files, which encapsulate an application. An image can be build on one machine, then uploaded to the container registry. The same application is distributed and can be deployed on multiple hosts.
Registry: A Registry is a service which stores container images.
Namespace: Namespaces allow managing repositories in a simple, clear and human-readable way. A namespace is a collection of container images having a unique identifier (each Namespace can only exist one time). A namespace belongs to a user, responsible for configuring the push and pull permissions.
Image: Container images are files that include all the requirements and instructions of a complete and executable version of an application. When running an image, it becomes one or multiple instances of that application. You can pull the image instructions, edit its settings, view its versions or delete it.
In the Tools section of the side menu, click Container Registry. If you do not have a Registry already created, the product presentation is displayed.
Click on Create a namespace to configure a new namespace.
Edit the following information about the namespace:
You can choose a region in which your namespace will be deployed geographically. Currently we provide the following locations:
FR-PAR: Paris, France
NL-AMS: Amsterdam, The Netherlands
A namespace can either be public or private. Everyone will be able to pull container images from a public namespace. Privacy policies may be set at image level.
Click the Create a namespace button. This action launches the namespace creation.
To use the namespace, make sure Docker is installed on the local computer.
1 . Retrieve the push instructions for the namespace by clicking on … > Push instructions:
2 . Log into the Namespace by running the following command from the command line:
docker login rg.fr-par.scw.cloud/mynamespace -u nologin -p $SECRET_KEY
$SECRET_KEYwith the Secret Key and
mynamespacewith the name of your Namespace.
3 . Once logged in, a confirmation is displayed:
1 . Pull the latest release of the Ubuntu docker image:
docker pull ubuntu:latest
2 . Tag the image:
docker tag ubuntu:latest rg.fr-par.scw.cloud/mynamespace/ubuntu:latest
3 . Push the image to the registry using docker:
docker push rg.fr-par.scw.cloud/mynamespace/ubuntu:latest
mynamespacein the examples abouve with the name of your namespace.
1 . Click on the identifier of the namespace to list its images:
2 . The list of images stored within the namespace displays:
1 . Click on … > Pull instructions to display pull instructions for an image:
2 . A popup displays the command line instructions to pull the image with docker:
3 . Copy the instructions and paste them into a terminal window to pull the image.
Scaleway Elements Container Registry supports versioning of files so you can distribute several releases of an image.
1 . Click on … > Versions to display a list of available versions of the image:
2 . A list of all available versions of the image is displayed:
3 . To view pull instructions for a specific version, click on … next to the version, then Pull instructions.
If a specific version is no longer required, click on … > Delete next to the identifier to delete it.
The image privacy policies specify whether everyone is granted to pull a container image or not.
To update this policies, click on …* next to the container image name, then on Privacy Policies.
The setting can either be Public, Private or Inherence from namespace policy.
Click on Update privacy policies to modify the policies.
To delete an image, click on … next to the image name, then on Delete.
Confirm the deletion of the image in the pop-up. This action is irreversible and all your data stored in the image will be deleted.
The Namespace privacy policies specify whether everyone is granted to pull a container image or not. Everyone will be able to pull container images from a public namespace.
To update the Namespace privacy policies, click on the Namespace Settings tab, then configure the policy by clicking on Public or Private.
Important: Each container image may have its own privacy policies.
It is possible to delete a namespace from the Namespaces list, by clicking on … > Delete.
A namespace can also be deleted from the Namespace Settings tab, by clicking on the Delete namespace Button.
This action is irreversible and all your data associated with this namespace will be deleted.