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 -->
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.
> 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 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Docker container information needs to be updated to reflect the lack of the latest tag and the presence of the master 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
has this been resolved? I can possibly help