No latest tag on dockerhub

[Panthro]

docker run -it -p 80:80 -e GITHUB_REPO=username/repo gitbook/nuts
Unable to find image 'gitbook/nuts:latest' locally
Pulling repository docker.io/gitbook/nuts
docker: Tag latest not found in repository docker.io/gitbook/nuts.

https://hub.docker.com/r/gitbook/nuts/tags/

[AaronO]

@Panthro This is semi intentional.

A lot of docker images on DockerHub only have one latest tag, and no version tags. I think that's a terrible practice, and that it's much more reliable to have immutable versioned releases. Whereas if you always use latest something may break without you ever noticing.

By using a specific tagged release, you get the peace of mind that the image you have will always be the same and won't randomly break on you. (Have one version on your laptop and another in production or staging)

[Panthro]

I recommend updating the docs then, I'm an experienced docker user and for me was easy to get the actual tag, for some new comers would be really hard:

http://nuts.gitbook.com/deploy.html

[AaronO]

@Panthro Good point. We should probably add a latest tag out of convenience.

But I really think it's sad that the docker community does not version seriously, it makes it hard to use things reliably in production. I end up maintaining most of our internal docker images due to this exact issue.

Versioning should be opt-in, but most images don't even have versions so that's impossible.

[Panthro]

I respectfully disagree =)

Take a look at the oficial images, node for instance: https://hub.docker.com/r/library/node/tags/

It has all sorts of tags, and they're all related to the middleware involved.

To get a node:5.x.x for instance, you can use node:5.1.11 OR node:5.1 (auto update minor releases) OR node:5.

This is the pattern that the own docker oficial images are following, and I believe with time the community will learn and follow.

BUT they also have the latest tag, for those who are running an experiment and want the bleeding edge or more patched version OR don't care at all.

[jessep]

I think the greater point is that the line you suggest running in the docs docker run -it -p 80:80 -e GITHUB_REPO=username/repo gitbook/nuts doesn't run successfully. I would recommend either updating the docs to include the current tag or add a :latest tag.

[dovinmu]

I'm new to Docker but wanted to use it for this project, so it would have been helpful for me to have the command in the docs to be just copy-and-paste runnable. You could also point out that you need to get a GitHub auth token.