AppArch Hub (image registry)
hub.apparch.io is the distribution point for AppArch analyzer (collector) images. Opened in a browser it shows a catalog of published images and their current versions; your CI pipeline pulls the images from here. All images are multi-arch (linux/amd64 + linux/arm64) - the right architecture is selected automatically.
Authentication
Section titled “Authentication”Pulls are authorized with your installation credential: the username is the installation id, the password is the installation key. This is not the project token - aa_proj_* is the collector’s bearer to your own Api and is rejected here.
echo '<installation-key>' | docker login hub.apparch.io -u <installation-id> --password-stdinThe panel builds this credential for you in the project’s CI setup section, ready to paste (see Registering a project). For per-CI-provider examples, see Adding the runner to CI. The installation key is issued with your licence and is held by whoever administers the installation.
Pulling images
Section titled “Pulling images”docker pull hub.apparch.io/collectors/dotnet:latestdocker pull hub.apparch.io/collectors/dotnet:1.0.2latest always points at the newest release; pin a version tag to stay on a specific release. Published tags are shown live in the hub catalog.
Common errors
Section titled “Common errors”The texts below are the Docker client’s standard messages (identical for every private registry):
| Message | Meaning | Fix |
|---|---|---|
authorization failed: no basic auth credentials | Not logged in | Run docker login hub.apparch.io |
login attempt … failed with status: 401 | Credential wrong, or the licence is revoked or expired | Check the installation id and key; the hub refuses a pull when the licence no longer allows it |
429 Too Many Requests | Rate limit hit | Wait a few seconds and retry |
Read-only
Section titled “Read-only”You cannot push to the hub - it is read-only at the protocol level. Images only ship from the AppArch release pipeline.