Skip to content

Scontain Image Registry

Since we ran into rate limitation issues with Docker hub, we needed to move to a new container image registry: You can register a free account at (see also below).

For new users: Please register an account

Please register a free account at

You need to confirm your email and, we will grant you - typically within a few hours - access to the community edition.

Create an access token

After you registered an account, you can create an access token for docker login as follows:

You can create a by

  • selecting a name of the token, e.g., docker_token
  • selecting scope read_registry and then
  • pressing button create personal access token.

Copy your new access token and use this for your docker login (see below)

For more information, please read this gitlab docu


SCONE Register Access Token

docker login

You can log into the registry as follows:

docker login

using your

  • your ID as username, and
  • your access token as password.

docker pull

When you execute a docker pull, you now need to specify the registry in each pull request.

Instead of pulling the image sconecuratedimages/crosscompilers:alpine like this:

docker pull sconecuratedimages/crosscompilers:alpine

you now need to pull this image like this:

docker pull

Password Reset

To reset your password, please visit

If you do not remember your email address or your login: You should have gotten an email regarding this and, you need to reset the password because you are given a random password.

You should have the same access rights as previously. If not, please let us know.

Searching for Container Images

One disadvantage of our registry is that finding images and tags using the GUI is not very comfortable. The advantage of the registry is, however, that it has an [API] ( that one can use to automate the searches. We show how to use this API.

API Token

Create an API Token at by

  • selecting a name of the token, e.g., api_token
  • selecting scope read_api and read_registryand
  • pressing button create personal access token.

Say, you store this token in an environment variable SCONE_HUB_ACCESS_TOKEN, i.e.,


Project IDs

Each image repository is associated with a project and each project has a unique project ID. To find the project ID for a image repository, let's say you want to find the project ID for a repo crosscompiler, you could do this as follows:

export REPO=crosscompiler
curl -s -H "PRIVATE-TOKEN: $SCONE_HUB_ACCESS_TOKEN" "$REPO" | jq '.[].id,.[].name'

This would output something like


saying that 17 is the project ID of repo sconecuratedimages/crosscompilers. You could now set the project ID and list all image tags of this repo:

export PROJECT_ID=$(curl -s -H "PRIVATE-TOKEN: $SCONE_HUB_ACCESS_TOKEN" "$REPO" | jq '.[].id')
curl -s -H "PRIVATE-TOKEN: $SCONE_HUB_ACCESS_TOKEN" "$PROJECT_ID/registry/repositories?tags=1" | jq '.[].tags[].name'

This will output many tags like


Now you can use the command line to search for the tags that you are interested in. Say, you want to search for all tags of SCONE version 3.5.0. In this case, you could define a patter scone5.3.0 and filter the output as follows:

export PATTERN="scone5.3.0"
curl -s -H "PRIVATE-TOKEN: $SCONE_HUB_ACCESS_TOKEN" "$PROJECT_ID/registry/repositories?tags=1" | jq '.[].tags[].name' | grep "$PATTERN"

The output might look as follows:


Common Project IDs

To simplify the search for tags, here are some common project IDs.

Project ID Repo Name