Comments on Docker Hub – why is there no lts tag?

[Starefossen]

I have had many questions as of late why we do not provide an lts tag. This was thoroughly discussed in #52 but I think it would beneficial to add something about lts / argon to the README of this repo and on Docker Hub.

Speaking of Docker Hub, there is a lot of unattended comments for the node image. I have opened docker/hub-feedback#579 in an attempt to have the Docker Hub gals and guys to provide a better way to comment on official images, or at least get a notification about new comments.

[chorrell]

Yep, totally agree. I've seen a few questions about an "lts" tag myself.

And thanks for opening docker/hub-feedback#579!

There doesn't seem to be an easy way to monitor comments there. It's something I've struggled with for a while. I'm not even sure if OPs get a notification if we respond to a given question and there's no way to "reply" to a specific comment. Honestly, as it is now I'd prefer if the comments were just disabled and people were directed to submit an issue here.

[Starefossen]

Maybe @tianon or @yosifkit could speak our case with the Docker Hub maintainers on docker/hub-feedback#579.

[2color]

👍

[mrsimonemms]

👍

To my mind, an LTS tag also makes sense. The only downside could be is that it could cause breaking changes on switchover day between the versions. However, that's something for the project maintainers to worry about, rather than the Docker maintainers.

[atd-schubert]

👍

[jsumners]

I think it is fairly obvious that when someone specifies LTS then they literally mean they want whatever the current LTS is. But if that is unacceptable, then simply append the LTS release number, e.g. LTS4 or LTS6.

[Starefossen]

There exists no LTS tags for any other official image, simply because this will break each time a new LTS is released. We already manage a lot of different tags for the Node.js Docker image and I am not inclined to add more than strictly necessary.

[SimenB]

Can be tracked in #527