TRG 4.05 - Container registries
| Status | Created | Post-History |
|---|---|---|
| Active | 20-Mar-2024 | Remove example workflow and refer to TRG 4.01 |
| Active | 04-May-2023 | Place DockerHub as mandatory container registry; remove GHCR references |
| Active | 05-Jan-2023 | Initial release |
| Draft | 14-Sept-2022 | n/a |
Why
Using a central container registry greatly improves security and manageability of images. It also makes it easier for external parties to validate that images are correct if they are coming from the same source.
Description
In Eclipse Tractus-X we are using one central container registry. This registry ist tractusx on DockerHub.
All container images released for an Eclipse Tractus-X product must be present on DockerHub. Also be aware of the necessary remarks for container images described in TRG 4-06 and alignment on common base images described in TRG 4.02.
Implementation
The example from TRG 4.01 shows a simple workflow, that can be used to publish your Docker image(s) to DockerHub.
It is using secrets, that contain credentials to authenticate at DockerHub. These secrets are present at GitHub organization
level and can therefore be used in any repository in our org.