Docker tag9/1/2023 ![]() ![]() The usability around which the Docker Registry HTTP API V2 was built was to have Immutable references to the Images. In such cases, we would require the tags to be mutable. But at times, situations arise where one wants to have even more readability, for ex., using the latest version of the resource every time or raising a small patch so that it reflects in the version. This is useful when versioning attached to the resources is immutable. It helps users to have a better control the specific resource that they are using. I haven't changed the Referenced for the Image, but its behaviour changed.Īccessing a resource from a collection of similar resources is always easy when there is a versioning attached to it. We tried many and this one is our favorite so far.I am unable to see my changes, even though I am using the referencing the image using the Correct Tag. Try it, adjust it as need it and do what it works best for you and your team. You can also define any other suffix for your tag that maps to the code version, so you can easily troubleshoot (e.g. So you know what is the most current commit so you can troubleshoot issues with a specific image and map back to the code to create fixes as needed. If you don't have a CI/CD yet, and you are doing this manually, just set the tag in that format manually (pretty much type the full string as is) and instead of a build number, use a commit short git hash (if you are using git): Then we deploy it as a hotfix, for example. We check out that commit hash from git and debug and fix the issue. We check our CI/CD service and that tells us what commit is the most current. ![]() ![]() If we find an issue, we have the build number in the tag 20171612.1 so we know the build no. If there's a bug in an environment with certain tag, we pull such tag, build and trobleshoot and reproduce the issue under that condition. And we keep track on what's deployed where. We don't create an independent build per environment. Then that build is deployed as needed to the different environments. So, when we merge, we create a single build.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |