---
title: "Getting the image | DRAWBRIDGE docs"
description: "How the pipeline builds and publishes the gateway image, and how to pull and verify a pinned release by its digest."
url: https://drawbridge.apps.wayne.edu/docs/deploying/getting-the-image.html
llms: https://drawbridge.apps.wayne.edu/llms.txt
generator: Squire agent-ready
---

# Getting the image [#](https://drawbridge.apps.wayne.edu/docs/deploying/getting-the-image.html#getting-the-image)

Pull the gateway image the pipeline publishes, and verify the one you pulled against the digest the publish job printed.

## Build and publish [#](https://drawbridge.apps.wayne.edu/docs/deploying/getting-the-image.html#build-and-publish)

The GitLab pipeline runs Preflight's `php-test` (PHP 8.3, 8.4, 8.5) and `composer-audit` components, a `composer-ci` job, `gateway-image:build` (Buildah, on merge requests and `main`), `gateway-image:publish` (on tags only) and a manual `rig` job. The pipeline builds the gateway image on every merge request and on the default branch, and publishes it to the stack's image registry (the group's `images` project) when a tag is pushed (base images come through the dependency proxy where there is one, else straight from Docker Hub, pinned by the Dockerfile either way). The image is at `<registry>/enterprise-apps/images/drawbridge-gateway:<tag>` (for example `<registry>/enterprise-apps/images/drawbridge-gateway:0.6.2`). `<registry>` is the stack's container registry; Enterprise Applications has its address. There is no `latest` tag: pin a release.

The image is built for linux/amd64, the architecture of Citadel's docker hosts. Check before you deploy: `docker manifest inspect <image>:<tag>` should list `amd64`. The 0.6.1 image was built for arm64 by mistake; use 0.6.2 or later.

## Pull the image [#](https://drawbridge.apps.wayne.edu/docs/deploying/getting-the-image.html#pull-the-image)

```sh
docker pull <registry>/enterprise-apps/images/drawbridge-gateway:0.6.2
```

## Verify the digest [#](https://drawbridge.apps.wayne.edu/docs/deploying/getting-the-image.html#verify-the-digest)

The publish job prints the digest it pushed. Verify the image you pulled against it:

```sh
docker inspect --format='{{index .RepoDigests 0}}' <registry>/enterprise-apps/images/drawbridge-gateway:0.6.2
```

## OCI labels [#](https://drawbridge.apps.wayne.edu/docs/deploying/getting-the-image.html#oci-labels)

The image carries OCI labels (`org.opencontainers.image.source`, `.revision`, `.version`, `.licenses`) set from the pipeline's commit; a local `docker build` leaves them empty.

## The module floor [#](https://drawbridge.apps.wayne.edu/docs/deploying/getting-the-image.html#the-module-floor)

The image also refuses to build if Debian serves apache2 or mod_auth_openidc below the versions the rig tested: the Dockerfile checks the installed versions with `dpkg --compare-versions` right after the install (apt-get has no `>=` syntax) and stops the build with a clear message when one is lower. The floor is apache2 2.4.69-1~deb13u1 (checked 2026-11-03) and mod_auth_openidc 2.4.17-1+deb13u1 (raised 2026-11-08 for CVE-2026-54789, a bug in the state-cookie parser), both against debian:trixie-slim. `DockerfileFloorTest` pins the floor, its position after the install, and the README documentation.

Note

To raise the floor, bump the two versions in the Dockerfile's install step and in `tests/Unit/DockerfileFloorTest.php`, which pins them.

## When to raise it [#](https://drawbridge.apps.wayne.edu/docs/deploying/getting-the-image.html#when-to-raise-it)

`composer advisories` is the advisory watch. It reads the floors and the Debian release from the Dockerfile, asks [OSV.dev](https://osv.dev/) (which republishes Debian's security tracker) which advisories still affect each floor version, and exits 1 when Debian has a fixed build above a floor, naming the advisory and the fix. An advisory Debian has not fixed yet is listed to watch and does not fail, and one Debian rates unimportant is only counted. Exit 2 means the Dockerfile or the feed could not be read, never a pass.

It needs the network, so it is not part of `composer ci`. The GitLab `advisories` job runs it from a pipeline schedule (weekly is plenty) or by hand from the pipeline page, and never on a merge request.

## The deploy layer [#](https://drawbridge.apps.wayne.edu/docs/deploying/getting-the-image.html#the-deploy-layer)

`site/` is the front page, a static sheet set for the gatehouse. On Citadel it is served by the raw-PHP deploy layer in `deploy/`: a Squire kit whose front controller serves `site/` behind HELMET's security headers. For local development, keep serving `site/` directly.

## Related [#](https://drawbridge.apps.wayne.edu/docs/deploying/getting-the-image.html#related)

- [Releasing](https://drawbridge.apps.wayne.edu/docs/deploying/releasing.html)
- [Proof](https://drawbridge.apps.wayne.edu/docs/reference/proof.html)
- [Try it without Entra](https://drawbridge.apps.wayne.edu/docs/guides/try-without-entra.html)
