Skip to main content

Container images

The Images workflow publishes five images to GitHub Container Registry for linux/amd64 and linux/arm64:

ImageContents
ghcr.io/jusso-dev/bower-collectorCollector: redaction, policy, durable queue and outputs
ghcr.io/jusso-dev/bower-managementManagement API with the bundled console
ghcr.io/jusso-dev/bower-webStandalone console on unprivileged nginx (details)
ghcr.io/jusso-dev/bower-sidecarDocker sidecar (details)
ghcr.io/jusso-dev/bower-cloudCloud agent for AWS SQS and Google Pub/Sub (AWS, GCP)

Tags​

TagPublished whenUse for
edgemanual Images dispatch on maintrying the last published main build
sha-<commit>each release or manual publicationpinning an exact build
X.Y.Z, X.Y, latesta vX.Y.Z tag is pushedproduction

Ordinary merges do not publish images. After CI passes, refresh edge with gh workflow run images.yml --ref main. See CI for the full validation cadence.

Pin production deployments by version or digest (@sha256:…), not edge.

Supply chain​

Each image carries an SPDX SBOM and SLSA provenance from BuildKit, plus a GitHub build-provenance attestation signed with the workflow's OIDC identity:

gh attestation verify oci://ghcr.io/jusso-dev/bower-sidecar:edge --owner jusso-dev
docker buildx imagetools inspect ghcr.io/jusso-dev/bower-sidecar:edge --format '{{ json .SBOM }}'

Configuring the published management image​

The published bower-management image is built without tenant settings. Configure the API and its bundled console at runtime:

Bower__Entra__TenantId=<tenant-id>
Bower__Entra__Audience=api://<api-client-id>
Bower__Console__ClientId=<spa-client-id>
Bower__Console__ApiScope=api://<api-client-id>/Bower.Access
Bower__Console__RedirectUri=https://bower.example.org # optional

The API serves these public SPA values as /config.js. Or run bower-web in front of the API and configure the console there instead.