docker container tags #31

Open
opened 2026-10-05 06:02:47 +02:00 by adam · 3 comments
Owner

Docker container information needs to be updated to reflect the lack of the latest tag and the presence of the master tag.

Docker container information needs to be updated to reflect the lack of the latest tag and the presence of the master tag. <!-- github-sync-id:3703913690 -->
Author
Owner

Would you be able to help me with this. I am not familiar with how docker works

Would you be able to help me with this. I am not familiar with how docker works <!-- github-comment-id:3793890672 -->
Author
Owner

Would you be able to help me with this. I am not familiar with how docker works

Pablo, I'm not overly proficient in docker or github so take this for what it may be worth. Looking at the tags for your github repo there is no latest tag. When trying to pull from Docker, looking for the latest tag, it was failing for me because of this. This issue lies, I believe, in the fact that you do not have a "latest" tag assigned to the most recent container image. From what I can find, you have to manually create a latest tag in github and point it to the container image you want to target. Then when you have a new container image, the tag has to be re-pointed to the new image. This is how you can control pulls to a stable release vs. the master branch or betas where you are making changes that could potentially break things.

As far as how to do this, I would have to look into it myself. There does seem to be some tag automation possibilities out there. This may help...https://github.com/marketplace/actions/latest-tag

> Would you be able to help me with this. I am not familiar with how docker works Pablo, I'm not overly proficient in docker or github so take this for what it may be worth. Looking at the tags for your github repo there is no latest tag. When trying to pull from Docker, looking for the latest tag, it was failing for me because of this. This issue lies, I believe, in the fact that you do not have a "latest" tag assigned to the most recent container image. From what I can find, you have to manually create a latest tag in github and point it to the container image you want to target. Then when you have a new container image, the tag has to be re-pointed to the new image. This is how you can control pulls to a stable release vs. the master branch or betas where you are making changes that could potentially break things. As far as how to do this, I would have to look into it myself. There does seem to be some tag automation possibilities out there. This may help...https://github.com/marketplace/actions/latest-tag <!-- github-comment-id:3795445928 -->
Author
Owner

has this been resolved? I can possibly help

has this been resolved? I can possibly help <!-- github-comment-id:5388011898 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshview#31