How easy it is to upgrade to Sitecore Management Services 4.1.0 with Docker

Initially, it wasn't easy for me to understand the concept of Docker image tags and the registry. The Sitecore slack channel was useful with this regard and many such scenarios because sometimes, it is about staying there and seeing what people talk and then you can easily pick up things. That is when I realized that Sitecore images are pushed into container registry and the tags are updated in this SCR image tags page.

So today, while accidentally going through Sitecore downloads, I realized why not upgrade the mvp site to SMS 4.1.0, a quick look up in the SCR image tags seemed to have a related image:

Just one change to .env file:

Although I had an error as per this blog, it seemed one-off and error was gone during the next compose-up and Sitecore push was successful, not to mention I changed the image tag as per this screen shot from 4.1-1809 to 4.1.0-1809 but unsure if that is the reason for the error!

Nevertheless, I love the advantage of using Docker images and tags. It is definitely tough when it gets flaky but that is where proper settings in the Docker / override files help. If you get through one cycle of deployment and debugging, Docker is good to setup local environment across machines!