You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@nudgegoonies Please explain in a bit more detail how you'd want tagging to work wrt git commits and branches. What kind of tooling is it you're using for mirroring?
We use Artifactory as Docker Repository and lstags for mirroring selected images from docker hub and other registries.
lstags does not support mirroring a specific SHA so we pull the latest image manually, tag it to a version, and push it to Artifactory. But even if lstags could mirror a sha, only providing latest is not a good idea in my opinion. For example when there is an incompatible update. Many images have 3 types of tags:
The moving tag latest that always points to the latest version.
The moving tag to the latest compatible version which is mostly the major version in semantic versioning.
And then immutable tags for every minor version pushed to the registry.
Actually there is only a latest tag. This is a problem where docker-images have to be reviewed and mirrored in internal registries.
The text was updated successfully, but these errors were encountered: