Published Docker images
Enterprise images are published under guidaapp on Docker Hub. There is no
single all-in-one guida-enterprise image in this release.
The current release is version 0.1.0-alpha.1, platform Linux amd64.
Use the recorded digests to identify the exact images; do not assume a latest
or semantic-version tag exists.
Image inventory
Section titled “Image inventory”| Repository | Role |
|---|---|
| guida-enterprise-api | Authorization, authoring, execution coordination and product APIs. |
| guida-enterprise-console | Browser interface and authenticated Console sessions. |
| guida-enterprise-migrations | One-shot database schema planning and application. |
| guida-enterprise-recovery | Operator recovery and consistency tools, including PostgreSQL tools. |
| guida-enterprise-local-seed | Synthetic local development bootstrap data. |
| guida-enterprise-document-worker | Configured retained-document processing on Linux. |
| guida-enterprise-local-document-credentials | Credential helper for the local development identity setup. |
Download the release image inventory. It contains immutable references. Use it to select matching images when preparing an installation. Matching Windows packages and checksums are on the downloads page.
The local seed and credential helper are tied to the development setup. Do not treat them as general provisioning tools for another identity provider.
Inspect an image without configuring a server
Section titled “Inspect an image without configuring a server”These commands use the exact migration image checked on 11 October. They run in PowerShell, Bash or another shell with Docker available and Linux containers enabled:
docker pull guidaapp/guida-enterprise-migrations@sha256:fc7660012d925e8e8c1a0f0f8a8b4af5150dd0d21177b6cec8c793199ba5123bdocker run --rm --network none guidaapp/guida-enterprise-migrations@sha256:fc7660012d925e8e8c1a0f0f8a8b4af5150dd0d21177b6cec8c793199ba5123b planThe plan command reads the embedded migration inventory. It does not connect
to a database or apply migrations. For this image, expect 59 migrations and
this plan hash:
db553e2f8a8b019e0979d625c70a99ede80edb091c25ecb6eafe0105a6168d32A successful plan confirms you can pull and run the packaged migration command. Continue with the installation guide to configure the server and execution hosts.
What is still required for an installation?
Section titled “What is still required for an installation?”The API and Console need configured PostgreSQL, identity, HTTPS, persistent storage and matching application settings. Studio tests need the separate Windows draft runner. Signed jobs need the appropriate enrolled execution host and revision trust.
The developer Compose setup still builds from a source checkout. The intended public bundle will pull matching images and provide the missing setup flow. Until then, follow operator-supported installation and review alpha availability.