Citadel's images#
Citadel runs every PHP app on one of its own Apache and PHP images. Parity runs the same image, byte for byte, and proves it before saying so. This page covers the catalog, the download, the check, and what Parity says when Citadel has not published an image yet.
The catalog#
Parity carries a catalog of Citadel's images inside the binary: each tag with its image id, the tar it comes from,
and that tar's sha256 and size. parity image list shows it, and whether each image is on this computer and
matches:
Parity image list the Citadel images Parity knows
[INFO] citadel/php-apache:8.5r3 not here; parity image get downloads it (379 MB)
[INFO] citadel/php-apache:8.4r5 not here; Citadel has not published a download for it yet
| Tag | PHP | Status |
|---|---|---|
citadel/php-apache:8.5r3 |
8.5.12 | downloadable and checked |
citadel/php-apache:8.4r5 |
8.4.27 | no download yet, until Citadel publishes its tar |
A new Citadel image means a new Parity release with a new catalog entry. --json gives the full image ids.
Getting one#
Citadel's images are docker save tars kept in git LFS in enterprise-apps/images on git.wayne.edu, so getting one
takes your own access there. parity image get fetches only the one tar, never the whole repository, and tries these
routes in order:
- A tar you downloaded yourself, named with
--file. Download it from the project's page in your browser, thenparity image get --file <the tar you saved>. The check is the same as for any other route. - A personal access token in
PARITY_GITLAB_TOKEN, used with GitLab's API.read_repositoryis enough. Parity reads it from the environment only and never prints it. - git LFS over SSH with your own key. Add
--httpsto clone over HTTPS instead, so git's credential manager signs you in.--gitpicks this route even when a token is set. The git route needs git LFS set up once: install git-lfs (it ships with Git for Windows and Homebrew hasgit-lfs), then rungit lfs install. Without it git fetches a small pointer file instead of the tar, and the error "git fetched a pointer, not the image" means exactly this.
The download goes to your user cache folder and is deleted once loaded; --keep keeps it.
Parity image get citadel/php-apache:8.5r3
✓ Fetch 379 MB with git LFS from git.wayne.edu (enterprise-apps/images) 30s
✓ sha256 61cbd26f1912 matches Citadel's tar
✓ Load loaded into docker 28s
✓ Id 950dcf67937a matches Citadel
citadel/php-apache:8.5r3 is Citadel's own, byte for byte. Next: parity up
What "matches Citadel" means#
Two checks, both against the catalog:
- the tar's sha256, before it is loaded, so a damaged or different download never reaches the engine;
- the loaded image's id, after, so the image the engine holds is the one Citadel runs.
Only an image that passes both is called Citadel's, in parity image get, parity up and parity check. An image
with Citadel's tag and a different id is reported as "not the build Citadel runs", and parity image get replaces it.
parity image verify repeats the check at any time, on the image here or on a tar with --file. Exit 1 when it
differs.
When Citadel has not published an image yet#
Parity runs Citadel's own images and nothing else. That is the point: an app that works here works on Citadel. So
when Citadel has not published the tar for a tag yet, Parity has nothing to download, and it says so instead of
guessing. parity up and parity check print:
✗ Image citadel/php-apache:8.4r5 is not on this computer yet.
Citadel has not published a download for citadel/php-apache:8.4r5 yet. Set image in parity.json to one
that parity image list can get, or ask the Citadel team to publish it.
parity up stops there with exit 2, as it does for any missing image. There are two ways on:
- Pick an image Parity can get. Set
imageinparity.jsonto a tag thatparity image listcan download (today,citadel/php-apache:8.5r3), then runparity image getandparity up. In the desktop app, the Images screen shows which tags have a download. - Ask the Citadel team to publish it. Once its tar is in
enterprise-apps/images, the next Parity release adds it to the catalog andparity image getdownloads it.
An image you built or pulled yourself under Citadel's tag still runs. Parity says it is not in the catalog, or not the build Citadel runs, so you know it cannot vouch for it.
On an arm64 computer (Apple Silicon, Windows on Arm, an arm64 Linux box), Citadel's amd64 image runs under Rosetta or QEMU emulation. Troubleshooting has the steps.