Appearance
Container Registries
Container registry connections provide credentials for Docker image update checks and Linux Runner jobs.
The service currently supports Docker Hub and custom OCI-compatible registries.
Registry Connections
Create a connection with the registry type, URL, and host used in image references. Public Docker Hub images often work anonymously. For private registries, store basic-authentication credentials or a bearer token in secret variables and select them on the connection.
Disable a connection to exclude it from image update checks.
Runner Image Pulls
In an infrastructure job, add one or more connections under the Docker registries build feature. The selected credentials are available to host Docker commands and registry tools inside execution containers. See Registry Credentials In Job Steps for requirements and usage. For authenticated pulls, the connection must be active, assigned to the selected pool, and match the image reference’s registry host exactly.
The Runner's workspace-ownership helper image is configured locally on the Runner. Its pull does not use container-registry features attached to a job. The image must already be present or allow an anonymous pull.
Image references without an explicit host use docker.io. A job without the build feature pulls anonymously. Multiple attached active connections for the same image host are ambiguous and prevent the job from starting.
Docker Image Tracking Rules
Docker image tags are not always a single linear version stream.
Some projects maintain multiple branches at the same time. For example, an image can publish 3.6.x and 3.7.x releases in parallel. In that case, blindly picking the newest semantic version would incorrectly recommend crossing from the maintained 3.6 branch to 3.7.
Tracking rules control how Ordyn selects a recommended newer tag for a repository.
Rules match by:
- registry host
- repository name
- optional tag pattern
The tag pattern supports * as a wildcard. Examples:
3.6.*8.**-alpine
More specific tag-pattern rules are evaluated before repository-wide rules.
Tracking Strategies
Same minor branch
Only tags with the same major and minor version are considered.
Example:
- current:
3.6.2 - allowed:
3.6.3 - ignored:
3.7.0
This is the default for tags with at least major and minor version components, such as 3.6 or 3.6.2.
Same major branch
Only tags with the same major version are considered.
Example:
- current:
8 - allowed:
8.0,8.1,8.2 - ignored:
9.0
This is the default for major-only semantic tags.
Newest stable semantic version
Every stable semantic version tag is considered, including major and minor upgrades.
Use this only for repositories where newer semantic tags represent a safe upgrade path.
Digest only
No newer tag is recommended.
Ordyn reports whether the current tag points to a different remote digest.
This is useful for floating tags such as latest, stable, or vendor tags that are not meaningful semantic versions.
Disabled
Matching images are ignored by update tracking.
Use this when a repository should remain inventoried but should not create Docker image update recommendations.
Suffix Preservation
Keep suffix preservation enabled to stay on the same image variant. For example, 1.2.3-alpine can update to a newer -alpine tag without switching to -bookworm or an unqualified tag.
Digest Drift
A digest drift means the current tag still has the same name, but the registry resolves that tag to different image bytes.
Example:
- local image:
redis:7.2@sha256:local-digest - registry reports:
redis:7.2@sha256:registry-digest
The UI shows this as Tag digest changed.
This is different from a version update. A version update means Ordyn found a different tag, such as 7.2.4.
Digest drift is common for floating tags and can also happen when vendors republish mutable tags.
Rechecking Images
Changing a tracking rule rechecks matching inventoried images. Endpoints do not need to submit another inventory before the new policy can apply.