You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to ask about the custom "version-specific" tags on Docker Hub. Specifically, I'm referring to tags like these:
feskol/gitlab:17-ce
feskol/gitlab:17.7-ce
feskol/gitlab:17.7.2-ce (this one is convenient as it avoids adding the ".0" suffix found in the original GitLab tag)
Personally, I use the full version tag without the ".0" suffix: feskol/gitlab:17.7.2-ce. I’m curious if anyone else uses these other version tags, or if I should remove them entirely.
The main reason for considering removal is how GitLab’s update process works. Sometimes, GitLab requires multiple upgrade steps, meaning you may need to perform several upgrades to get from your current version to the target version. To do that, you would need to use the full version tag (for example the 17.7.2-ce or 17.7.2-ce.0 ).
The only case I can think of for using these custom "version-specific" tags is if, for example, you have a cron job running docker pull to update the image, and you want to maintain a specific version, such as the "17.7" or "17.6" version.
These tags would still remain:
feskol/gitlab:17.7.2-ce.0 <- Original GitLab Version tag
feskol/gitlab:ce <- latest CE-Version
feskol/gitlab:ee <- latest EE-Version
feskol/gitlab:latest <- latest CE-Version (same as the ce-tag)
What do you think? Do you use these custom tags? Should I keep them or remove them?
Keep or remove the custom "version-specific" tags
Keep them!
0%
Remove them!
0%
Remove them but keep the one without the ".0" suffix.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I wanted to ask about the custom "version-specific" tags on Docker Hub. Specifically, I'm referring to tags like these:
17-ce
17.7-ce
17.7.2-ce
(this one is convenient as it avoids adding the ".0" suffix found in the original GitLab tag)Personally, I use the full version tag without the ".0" suffix:
feskol/gitlab:17.7.2-ce
. I’m curious if anyone else uses these other version tags, or if I should remove them entirely.The main reason for considering removal is how GitLab’s update process works. Sometimes, GitLab requires multiple upgrade steps, meaning you may need to perform several upgrades to get from your current version to the target version. To do that, you would need to use the full version tag (for example the
17.7.2-ce
or17.7.2-ce.0
).The only case I can think of for using these custom "version-specific" tags is if, for example, you have a cron job running
docker pull
to update the image, and you want to maintain a specific version, such as the "17.7" or "17.6" version.These tags would still remain:
17.7.2-ce.0
<- Original GitLab Version tagce
<- latest CE-Versionee
<- latest EE-Versionlatest
<- latest CE-Version (same as thece
-tag)What do you think? Do you use these custom tags? Should I keep them or remove them?
0 votes ·
Beta Was this translation helpful? Give feedback.
All reactions