Skip to content

Container Release Policy

17 April 2019

Container images are an increasingly popular tool for shortening the software development life cycle, allowing for speedy deployment of new software versions or additional instances of a service. Select services in the OSG Software Stack will be distributed as container images to support VOs and sites that are interested in this model.

This document contains policy information for container images distributed by the OSG Software Team.

Contents and Sources

Similar to our existing RPM infrastructure, container image sources, build logs, and artifacts will be stored in publicly available repositories (e.g. GitHub, Docker Hub) for collaboration and traceability. Additionally, container images distributed by the OSG Software team will be based off of the latest version of a supported platform with software installed from OS, EPEL, and OSG release Yum repositories with select packages installed from osg-development.


OSG Software container images will be tagged with at least one of the following tags:

Tag Description
fresh Images that build successfully and pass automated tests. Intended for users that need the latest fixes and features.
timestamp Each fresh image is also tagged with a timestamp reflecting their build date and time. Intended for rollback in case of issues with the current fresh image.
stable fresh images that pass acceptance testing; approved by the Release Manager. Intended for stable production use.


The OSG will keep images based on the Docker Hub image retention policy. In summary, container images that have not been pulled or updated in 6 months will be removed.


Container images that have been tagged as stable will be noted in the OSG release notes and announcements.

Change Log

  • 14 August 2020: Updated cleanup policy to match Docker Hub image retention policy.