`latest` tag not updated

[codeboten]

The latest tag in dockerhub isn't getting updated during the release process. This is causing user confusion.

[Aneurysm9]

Can we remove it? I've never been a fan of using mutable tags in this manner.

[jpkrohling]

I think we should not remove tags that were published, this could break people currently using it.

Related to #54

[codeboten]

Can we remove it? I've never been a fan of using mutable tags in this manner.

I'm not a fan of it either, but people (myself included) do use them and we've already been publishing it. I would prefer we keep it updated moving forward.

[mhellsten-ml]

This is still an issue. Having the "latest" tag point the latest stable release is Docker community standard, so I don't think this is just a matter of preference or style. People who don't want to pull the latest when they relaunch would/should use a version-specific tag. Thanks.

[delanym]

Delete it, let the 2 people (or was it 3?) who still rely on this old tag for their mission critical telemetry systems (is there such a thing?) quickly fix the issue, and we can all get on with our lives. Having an invalid tag hanging around confusing everyone is worse.

[mhellsten-ml]

Delete it, let the 2 people (or was it 3?) who still rely on this old tag for their mission critical telemetry systems (is there such a thing?) quickly fix the issue, and we can all get on with our lives. Having an invalid tag hanging around confusing everyone is worse.

This isn't for production so much as development: People who throw up a local stack of supporting services typically expect to get the latest stable release on the latest tag. When the behavior of the container that comes up doesn't match the documentation it's very confusing. 2 or 3 people commenting on this issue doesn't mean it's the entire universe of people this affects.

[dyladan]

This is causing active confusion with users. Either fix the tag or remove it but leaving it broken is misleading and the worst of both worlds. latest tag is a docker community idiom that many (most?) users not only expect to work but are frustrated when it doesn't. I very often use the latest tag of docker images as a branch in integration tests so that we can catch issues without having to manually modify the version matrix.

[bogdandrutu]

Updated the latest tag to 0.56.0, using manifest and image group as the base tag.

Commands for contrib (same for core image):

docker pull otel/opentelemetry-collector-contrib:0.56.0-386

docker pull otel/opentelemetry-collector-contrib:0.56.0-amd64

docker pull otel/opentelemetry-collector-contrib:0.56.0-arm64

docker tag otel/opentelemetry-collector-contrib:0.56.0-386 otel/opentelemetry-collector-contrib:latest-386

docker tag otel/opentelemetry-collector-contrib:0.56.0-amd64 otel/opentelemetry-collector-contrib:latest-amd64

docker tag otel/opentelemetry-collector-contrib:0.56.0-arm64 otel/opentelemetry-collector-contrib:latest-arm64

docker push otel/opentelemetry-collector-contrib:latest-386

docker push otel/opentelemetry-collector-contrib:latest-amd64

docker push otel/opentelemetry-collector-contrib:latest-arm64

docker manifest create otel/opentelemetry-collector-contrib:latest --amend otel/opentelemetry-collector-contrib:latest-386 --amend otel/opentelemetry-collector-contrib:latest-amd64 --amend otel/opentelemetry-collector-contrib:latest-arm64

docker manifest push docker.io/otel/opentelemetry-collector-contrib:latest