Skip to content

Git

STACKIT Git is a fully managed Git service that simplifies version control and collaboration for software development teams. It enables developers to securely host, manage, and track their codebase in the European cloud while maintaining full control over their projects.

  • announcement

    Faster image pulls and stricter isolation for STACKIT runners

    Section titled “Faster image pulls and stricter isolation for STACKIT runners”

    On November 12, 2026, we update the STACKIT runners of STACKIT Git Pipelines. Runner jobs pull the base images that we offer from an internal cache, and Docker operations that require privileged access to the runner host are no longer allowed. This makes image pulls faster and more consistent, and enforces a stronger separation between jobs.

    Base images are pulled from an internal cache

    Section titled “Base images are pulled from an internal cache”

    The runners pull the base container images that STACKIT offers from a cache on an internal registry, which shortens the time a job waits for its image. The STACKIT Container Registry is the upstream source of the cache. If the cache cannot serve an image, the runner pulls it from the STACKIT Container Registry, so pulls continue during periods of high traffic.

    Because the base images come from vetted copies in our own registry, your jobs are not affected by the rate limits of third-party registries, and your builds run in a consistent environment.

    Docker operations that need access to the runner host are rejected

    Section titled “Docker operations that need access to the runner host are rejected”

    To enforce a stronger separation between jobs on shared runners, the runners reject Docker commands that would give a container privileged access to the runner host. A job that runs such a command fails with an error message that starts with Command denied by Stackit Classic runner security policy.

    These operations are no longer allowed:

    • Running privileged containers, for example with docker run --privileged.
    • Adding Linux capabilities, for example with docker run --cap-add=NET_ADMIN.
    • Sharing the process or IPC namespace of the host with --pid=host or --ipc=host.
    • Mounting system paths of the runner host, such as /, /etc, /proc, /sys, /dev, /var, or /run, including their subdirectories. This includes mounting the Docker socket with -v /var/run/docker.sock:/var/run/docker.sock.

    You can still pull images, push images, run docker build and docker buildx build, and start unprivileged containers that mount the workspace, /tmp, or named Docker volumes.

    If your pipeline depends on one of these operations, contact our Help Center.

    We resolved an intermittent issue where concurrent Git operations cloning actions caused errors that make the job fail. Workflows should no longer fail unexpectedly on checkout steps.

    We are adding more base images to the cache. If your workflows rely on a standard base image, request it through our Help Center and include:

    • The image name. We only accept requests for official images.
    • The exact tags that you need, for example ubuntu:22.04 or node:20-alpine.

    If you have any questions, our STACKIT Help Center is always at your disposal.

    We are actively populating our pre-warmed action cache to keep step runtimes as fast as possible. If your workflows rely on custom, internal, or non-standard actions that you would like pre-cached on our runner images, please reply here with the action repository and version tag (e.g., owner/action-name@vX). We will evaluate and add frequently requested actions to the warm cache pool.

  • changed

    Forgejo Runner v13: changes that can break your workflows

    Section titled “Forgejo Runner v13: changes that can break your workflows”

    We have upgraded the runners of STACKIT Git to Forgejo Runner v13. This release makes expression evaluation stricter, removes legacy workflow commands, limits registry credentials to the job that declares them, and removes the remaining Gitea compatibility. Several cases that used to log a warning now fail the run, so check your workflows for the changes below.

    Invalid expressions and matrices fail the run

    Section titled “Invalid expressions and matrices fail the run”

    An expression that cannot be evaluated, such as a format() call with fewer arguments than its format string references, now fails the step or job instead of logging a warning. Attempting to exclude a value from a matrix that was never defined in that matrix now causes an error and prevents the workflow from running.

    Check the expressions and matrix definitions in your workflow files.

    The ::set-output, ::set-env and ::add-path commands no longer have any effect, and ACTIONS_ALLOW_UNSECURE_COMMANDS does not enable them again. Write to the environment files instead:

    • Replace echo "::set-output name=var::value" with echo "var=value" >> "$FORGEJO_OUTPUT".
    • Replace echo "::set-env name=VAR::value" with echo "VAR=value" >> "$FORGEJO_ENV".
    • Replace echo "::add-path::/custom/bin" with echo "/custom/bin" >> "$FORGEJO_PATH".

    The runner no longer logs in to registries with the DOCKER_USERNAME and DOCKER_PASSWORD secrets, because these credentials could be sent to a registry they were not meant for. If a job uses an image from a private registry, declare the credentials in that job:

    jobs:
    build:
    container:
    image: private.registry.example/app:latest
    credentials:
    username: ${{ secrets.REGISTRY_USER }}
    password: ${{ secrets.REGISTRY_TOKEN }}

    The ${{ gitea.* }} context is no longer supported. Replace it with ${{ forgejo.* }} in your workflows.

    The runner no longer attaches a terminal to the output of a step. Commands that print colors only when they detect a terminal now print plain text. To get colored output again, set FORCE_COLOR=1. Commands that require a terminal will now fail. For example, replace docker run -it with docker run -i.

    • Docker Engine 25.0 or later is required. We recommend 28.0.1 or later, because earlier versions can fail to create IPv6 networks with Forgejo Runner v13.
    • The GITEA_DEBUG, GITEA_TRACE, GITEA_RUNNER_CAPACITY, GITEA_RUNNER_FILE, GITEA_RUNNER_ENVIRON and GITEA_RUNNER_ENV_FILE variables are ignored. Remove them from your runner configuration and environment.
    • The container.network_mode option is removed. Use container.network instead.

    For more details, see the release announcement of Forgejo Runner v13.0 and the release notes of Forgejo Runner.

    If you have any questions, feel free to contact our Help Center.

  • announcement

    One SSH address for all STACKIT Git instances

    Section titled “One SSH address for all STACKIT Git instances”

    On October 27, 2026, from 20:00 to 23:00 (UTC), SSH access to STACKIT Git moves to one shared address. The name of your instance becomes the first element of the repository path. This reduces the publicly exposed surface of your instance and lets us improve the reliability of Git operations over SSH in one place.

    • Previous address: git@ssh.<instance>.git.onstackit.cloud:<owner>/<repository>.git
    • Address after the maintenance: ssh://git@ssh.git.onstackit.cloud/<instance>/<owner>/<repository>.git

    During the maintenance every Git instance is restarted once and is unavailable for about one minute. The restarts are staggered, so not all instances are affected at the same time. Access over HTTPS, your repositories, your users, your registered SSH keys and your IP allowlists do not change.

    The previous address keeps working until April 27, 2027. Your existing clones and your automation continue to work after the maintenance, so you can move them at your own pace. We remind you before we switch the previous address off.

    • Allow outbound traffic to 213.17.16.145 on port 22, if your network restricts outbound connections.
    • Add the host key of ssh.git.onstackit.cloud, if your systems verify host keys. Its fingerprint is SHA256:I4jgl6ALgx5qOWwpQVC2M613dV7R0Wy6LfQQ5LQKwR4 (ED25519).
    • Make sure the SSH key your client offers to ssh.git.onstackit.cloud is registered in your instance.
    • Identify every place that holds the address: local clones, build pipelines, deployment automation, infrastructure as code module sources and repository mirrors.

    Update the remote address of each repository:

    Terminal window
    git remote set-url origin "$(git remote get-url origin | sed -E 's#^(ssh://)?git@ssh\.([^.]+)\.git\.onstackit\.cloud[:/]#ssh://git@ssh.git.onstackit.cloud/\2/#')"

    For the full instructions, including how to select the right key when you work with more than one SSH key, see Connect to your repositories with SSH.

    If you have any questions, our Help Center is always at your disposal.