You are not logged in. Click here to log in.

codebeamer Application Lifecycle Management (ALM)

Search In Project

Search inClear

How to Access the Latest Docker Snapshot

This page describes the way of accessing the latest Docker snapshot, and also provides troubleshooting steps to resolve an access issue.



The following Docker setup is only for Evaluation purposes. Issues caused by using these snapshots are not taken care of by the Intland Support Team. Findings in the snapshot will be not fixed by the Intland Development Team.

Accessing the Latest Docker Snapshot

To access the latest Docker snapshot, run the below commands:

  1. docker login -u intlandsnapshot -p 89bc690e-bf19-4014-885b-7cd4c6355ca2
  2. docker pull intland/codebeamer-snapshot:latest
  3. docker logout

To get specific versions, use the following versioning schema for the tag:

<Codebeamer Version><date YYYYMMDD>


A few examples:

  • intland/codebeamer-snapshot:2.1-20240201
  • intland/codebeamer-snapshot:2.1-20240202
  • intland/codebeamer-snapshot:2.0-20231215
  • intland/codebeamer-snapshot:22.10-SP9

Access the Full TAG List Programmatically

To get the full list of available packages, run the following short bash script:

export DOCKER_USERNAME="intlandsnapshot"
export DOCKER_PASSWORD="89bc690e-bf19-4014-885b-7cd4c6355ca2"
export TOKEN=$(curl -s -H "Content-Type: application/json" -X POST -d '{"username": "'${DOCKER_USERNAME}'", "password": "'${DOCKER_PASSWORD}'"}' https://hub.docker.com/v2/users/login/ | jq -r .token)
curl -s -H "Authorization: JWT ${TOKEN}" "https://hub.docker.com/v2/repositories/intland/codebeamer-snapshot/tags?page_size=100" | jq -r '.results|.[]|{tagName: .name, date: .last_updated}'

Troubleshooting

In case the "Access is forbidden with a JWT issued from a personal access token." error message is displayed, perform the following steps:


  1. Open ~/.docker/config.json (Windows: C:\Users\<username>\.docker)
  2. Remove the "credsStore": "desktop.exe"line.
    • Make sure to delete the comma from the preceding line.
  3. Try to run the Docker login command again.