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


1.  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.

1.1.  Prebuilt Container Image

1.1.1.  Naming and Tagging Convention

The naming and tagging convention for the container image follows the pattern

comanage-registry-cron:<version>-<build number>

where

  • <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

1.1.2. 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.

1.1.3. Latest Tag

Beginning with version 4.3.0 the repositories also use the "latest" tag.

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. 


1.1.4. Repositories and Downloading Images

The prebuilt container image provided by the COmanage Project are available from three public repositories. The images available from the repositories are the same so you may choose the repository most convenient for you.

  1. dockerhub

    docker pull comanageproject/comanage-registry-cron:<version>-<build number>
  2. Amazon ECR Public Gallery

    docker pull public.ecr.aws/cilogon/comanage-registry-cron:<version>-<build number>
  3. GitHub Package Registry

    docker pull ghcr.io/cilogon/comanage-registry-cron:<version>-<build number>

1.2. Building the Image

The provided build script may also be used to build the cron image. See the build script help message for details.

1.3. Using the Image

1.3.1.  Preliminaries

The prerequisites for deploying the cron image are the same as for the Registry image except for the authentication and HTTPS details, since the cron image does not run a web server and does not require authentication.

1.3.2.  Configuration

The container configuration for the cron image is the same as for the Registry image except for any authentication and HTTPS details, since the cron image does not run a web server and does not require authentication.

See especially the environment variables COMANAGE_REGISTRY_CRON_USER and COMANAGE_REGISTRY_CRONTAB.

1.3.3. Example

Example deployments are included with the Registry container examples.

2. OpenLDAP slapd

TBD


  • No labels