Docker container versioning not implemented

[crisidev]

Hi,
I am using pushgateway and I would like to use the official prom/pushgateway container from docker hub.
The versioning system is not implemented and currently prom/pushgateway:latest contains pushgateway 0.2.0. Is it possible to push containers with a sane versioning system?

[beorn7]

@discordianfish We need Docket help! What is @crisidev talking about? :)

[crisidev]

I am speaking about the fact that prom/pushgateway docker containers on docker hub are pushed as just latest tag and not also with the correct version as tag. Example: current version of prom/pushgateway:latest is 0.2.0. Can you also push 0.2.0 as tag?

[fabxc]

Did the same as for node_exporter.

[crisidev]

Thanks!

[discordianfish]

@grobie: What are your plans with the binary builds? I was waiting for that with looking into how to fix this tagging issue properly.. Docker hub doesn't track remote tags which sucks.. We should either create our own images and push them to the hub - or switch things to quary.io which supports tacking of all tags.

[jimmidyson]

@discordianfish Docker hub can track git tags now, but only on new tag push. Mapping git tag name -> docker tag name.

[sdurrheimer]

This is fixed by #76. Future iteration of releases will have a sane docker image versioning.

• master tag for the latest commit in the master
• x.x.x-x tag for new pre-release
• x.x.x and latest tag for new release