Download Images and Bundles

Use MTG-provided repository credentials to download Management images, release bundles and update bundles from repo.mtg.de. Talos boot media is available through separate public download links.

Check the Docker and Podman Version Requirements before running the commands below.

Choosing the right Download

Image repository Purpose and tag

Image repository	Purpose and tag
`repo.mtg.de/releases/ers/vapp/management`	Management application image. Use the Management tag supplied by MTG.
`repo.mtg.de/releases/ers/vapp/release-bundle`	Full installation and recovery content. The tag is the appliance release to install or recover.
`repo.mtg.de/releases/ers/vapp/update-bundle`	One supported update transition. The tag has the form `SOURCE-to-TARGET`. Both versions must match a transition published by MTG.

repo.mtg.de/releases/ers/vapp/management

Management application image. Use the Management tag supplied by MTG.

repo.mtg.de/releases/ers/vapp/release-bundle

Full installation and recovery content. The tag is the appliance release to install or recover.

repo.mtg.de/releases/ers/vapp/update-bundle

One supported update transition. The tag has the form SOURCE-to-TARGET. Both versions must match a transition published by MTG.

Management and bundle images have separate purposes. An update bundle is available only for a published source-to-target transition; do not assume that an update exists for every pair of releases. See Files and Bundles.

Enter the MTG repository username. The selected runtime then prompts for the MTG-provided password or token. Continue only after login succeeds.

Docker

The export examples use docker image save --platform. Both the Docker CLI and engine must meet the version requirements above.

read -r -p 'MTG repository username: ' MTG_REPOSITORY_USER
docker login repo.mtg.de --username "$MTG_REPOSITORY_USER"

Podman

For the rootful Podman quick start, use a root shell on the Linux host. Use the same Podman user for login, pull, save and run. Rootful and rootless image stores are separate.

read -r -p 'MTG repository username: ' MTG_REPOSITORY_USER
podman login repo.mtg.de --username "$MTG_REPOSITORY_USER"

Select and download Images

Replace the placeholder tags with those supplied for your release. These settings apply to either runtime. Pull only the images required for your task.

Management runs the bundle’s Operations code on its own CPU architecture. Select the same platform as the destination Management engine, even though the appliance nodes use AMD64. Use linux/arm64 when the destination engine is ARM64 and MTG supplies that variant.

MANAGEMENT_PLATFORM='linux/amd64'
MANAGEMENT_TAG='REPLACE_WITH_MTG_MANAGEMENT_TAG'
RELEASE_TAG='REPLACE_WITH_APPLIANCE_RELEASE'
UPDATE_TAG='REPLACE_WITH_SOURCE-to-TARGET'

MANAGEMENT_IMAGE="repo.mtg.de/releases/ers/vapp/management:${MANAGEMENT_TAG}"
RELEASE_IMAGE="repo.mtg.de/releases/ers/vapp/release-bundle:${RELEASE_TAG}"
UPDATE_IMAGE="repo.mtg.de/releases/ers/vapp/update-bundle:${UPDATE_TAG}"

Docker

docker pull --platform "$MANAGEMENT_PLATFORM" "$MANAGEMENT_IMAGE"
docker pull --platform "$MANAGEMENT_PLATFORM" "$RELEASE_IMAGE"
# Only when MTG has published the required update transition:
docker pull --platform "$MANAGEMENT_PLATFORM" "$UPDATE_IMAGE"

Podman

podman pull --platform "$MANAGEMENT_PLATFORM" "$MANAGEMENT_IMAGE"
podman pull --platform "$MANAGEMENT_PLATFORM" "$RELEASE_IMAGE"
# Only when MTG has published the required update transition:
podman pull --platform "$MANAGEMENT_PLATFORM" "$UPDATE_IMAGE"

A successful pull puts the image in the selected runtime’s local image store. It does not install an update or import a bundle into Management.

Save Management for Transfer

Save the Management image, transfer the file to the disconnected host, then load it with that host’s runtime. Use a Docker-format archive to retain Management’s health-check metadata.

Docker

docker image save --platform "$MANAGEMENT_PLATFORM" --output management.docker.tar "$MANAGEMENT_IMAGE"
# On the destination Docker host, after transferring the file:
docker image load --input management.docker.tar

Podman

podman save --format docker-archive --output management.docker.tar "$MANAGEMENT_IMAGE"
# On the destination Podman host, after transferring the file:
podman load --input management.docker.tar

Save Bundles for Browser Upload

Browser uploads of release and update bundles require an OCI image archive with its full tagged image reference. Export the complete bundle image; do not use container filesystem export or extract only the inner content file.

Docker

Use Docker’s containerd image store to save the bundle directly as an OCI-compatible archive. It must be enabled in the engine used for the pull and save. Export one tagged bundle image for the destination Management platform:

docker image save --platform "$MANAGEMENT_PLATFORM" --output release.oci.tar "$RELEASE_IMAGE"

# Only for a published update that you pulled above:
docker image save --platform "$MANAGEMENT_PLATFORM" --output update.oci.tar "$UPDATE_IMAGE"

Upload the saved file directly to Management. No conversion tool is required. The classic Docker image store produces a different archive layout; changing the filename to .oci.tar does not change that format.

Podman

podman save --format oci-archive --output release.oci.tar "$RELEASE_IMAGE"
# Only for a published update that you pulled above:
podman save --format oci-archive --output update.oci.tar "$UPDATE_IMAGE"

The archives must retain the full repo.mtg.de/…:tag reference. Upload the resulting release or update archive through Settings > Bundles > Add bundle > Computer > Release or update. Wait until Management reports the bundle as available and check its target version and, for updates, its source version. See Manage bundles and registries.

Credentials and Verification

Repository credentials are separate from the mtg-admin account used to sign in to Management. A successful local CLI login does not populate Settings > Registries. Configure that connection separately if Management will retrieve bundles itself.

Keep certificate verification enabled when logging in and pulling. For a company proxy or private CA, configure trust in the container engine. Record the image reference and digest reported by the pull with your deployment records. Verify transferred files against their recorded SHA-256 checksums before loading or uploading them.

After completing downloads, remove the local registry login when it is no longer needed:

Docker

docker logout repo.mtg.de

Podman

podman logout repo.mtg.de

For CLI details, see Docker image save and Podman save.

Public Talos Boot Media

Management links to the public Talos boot-media directory. These downloads do not require MTG repository login. They are separate from the Management ISO directory.

These links are for Talos 1.13.7, the component version listed in the release catalog. Always use the version, platform and guest-agent choice shown by Download and boot the Talos artifact for your selected release. If that page specifies another version, use its links instead.