How to re-tag a blazeVSE image once you have a new container image
search cancel

How to re-tag a blazeVSE image once you have a new container image

book

Article ID: 216929

calendar_today

Updated On:

Products

BlazeMeter

Issue/Introduction

How to re-tag a blazeVSE image once you have a new container image

 

 

Environment

Release : 1.0

Component : BLAZEMETER MOCK SERVICES

Resolution

Assuming that there is a new container image that can be downloaded from <containerUrl> (for example gcr.io/verdant-bulwark-278/blazemeter/blazevse:5.0.3-somefix), you can. use docker pull to pull it:
docker pull <containerUrl>
Once the container image has been pulled, you need to re-tag it so that the Crane agent will use it instead of the production image.  Using  gcr.io/verdant-bulwark-278/blazemeter/blazevse:5.0.3-somefix as an example, if the production image is currently blazemeter/blazevse:5.0.3, you will need to re-tag the new image with 3 different tags
  1. Re-tag it as the same tag as the production image from gcr.io/verdant-bulwark-278/blazemeter/<component>:<version>, where component is the Crane component that the image is for (blazevseservice-mock, etc) and version is the production version (5.0.3)
  2. Re-tag it as blazemeter/<component>:latest, where component is the Crane component that the image is for (blazevseservice-mock, etc)
  3. Re-tag it as blazemeter/<component>:<version>, where component is the Crane component that the image is for (blazevseservice-mock, etc) and version is the production version (5.0.3)
docker tag gcr.io/verdant-bulwark-278/blazemeter/blazevse:5.0.3-somefix gcr.io/verdant-bulwark-278/blazemeter/blazevse:5.0.3
docker tag gcr.io/verdant-bulwark-278/blazemeter/blazevse:5.0.3-somefix blazemeter/blazevse:5.0.3
docker tag gcr.io/verdant-bulwark-278/blazemeter/blazevse:5.0.3-somefix blazemeter/blazevse:latest
(edited)