The container images detailed below compliment container deployments of Registry but they are not required for use with Registry.
Beginning with version 4.3.0 the images are multi-platform (aka multi-arch). Currently the platforms/architectures supported include
- amd64
- arm64v8
| Table of Contents |
|---|
crond
The crond container may be used to schedule asynchronous execution of Registry Jobs. The container image uses the same base as the Registry images but runs the standard cron daemon as a foreground process.
...
<version>is the Registry version number, for example 4.1.2<build number>is an increasing integer updated each time a new image is built
Automated Builds
The images are automatically built once each week to pick up changes in the underlying code and libraries. Each time a new image is built the <build number> increases.
Latest Tag
Beginning with version 4.3.0 the repositories also use the "latest" tag.
| Warning |
|---|
At this time the project has not implemented automated testing of each image built weekly by the automated build tooling. Deployers are strongly encouraged to not rely on the "latest" tag for production use and to implement thorough local testing of an image before putting it into production. |
Repositories and Downloading Images
...