

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Difficulty: 4
click for more info
Not enough gems
Cost: 6 gems
1: Publishing to Docker Hub
incomplete
2: Publishing to Docker Hub
incomplete
3: Delete and Pull
incomplete
4: Tags
incomplete
5: Latest
incomplete
6: The Bigger Picture
incomplete
This lesson's interactive features are locked, please to keep using them
If you look closely, you'll notice that your old version is tagged "latest"... that's a bit confusing. As it turns out, the latest tag doesn't always indicate that a specific tag is the latest version of an image. In reality, latest is just the default tag that's used if you don't explicitly supply one. We didn't use a tag on our first version, that's why it was tagged with "latest".
The convention I'm familiar with is to use semantic versioning on all your images, but to also push to the "latest" tag on your most recent image. That way you can keep all of your old versions around, but the latest tag still always points to the latest version.
So, for example, if I were updating an application to version 5.4.6, I would probably do it like this:
docker build -t bootdotdev/awesomeimage:5.4.6 -t bootdotdev/awesomeimage:latest .
docker push bootdotdev/awesomeimage --all-tags