azure-vote.yaml
we see that we are defining the container images for our back-end and front-end applications as pulling redis
and microsoft/azure-vote-front:v1
respectively.minimal images
.Dockerfile
and storing this in our private registry on ACR.pwd
and verifying the result displays $HOME/snyk-azure-resources/
. Our repo contains a submodule
that points to the source for the official redis image which happens to include a Dockerfile. To synchronize the submodule, type the following command:ls -a
command will show the contents and you will see a Dockerfile
in that directory. You can open this in your favorite editor like Microsoft Visual Studio Code and review the contents. The top few lines should look similar to this:Dockerfile
later, but for now, take note that the underlying base image is debian:buster-slim
.app/redis/6.0/
directory, we will build and tag our own container image using the provided Dockerfile
. To do so, we will run the docker build
command as follows:docker tag
commands to tag our image with the fully qualified name of your ACR login server. We are going to make this interesting by querying the value of our ACR login server using the Azure CLI within our docker tag
command. To do this, we will invoke az acr show
and specify our registry name while formatting our output with the -o tsv
parameter for plain text.version
and we will tag it a second time with latest
.docker push
on our tagged images and store these in ACR. Let's start with the first tagged image v1
:latest
:my-redis
repository matches what we pushed, we can run the following command: