< Previous Solution - Home - Next Solution >
This is PATH B: Use this path if your students understand Docker, don’t care about building images locally, and/or have environments issues that would prevent them from building containers locally. In this path, your students will be given a Dockerfile, will create an Azure Container Registry, and then will use ACR tasks to build the images natively inside ACR.
The students will need to be able to run the Azure CLI. Ideally this would be run from their local workstation, but it could also be the Azure Cloud Shell.
The coach should demonstrate running the application locally. To run the Fab Medical application locally:
npm install
node ./server.js &
http://localhost:3001/speakers
CONTENT_API_URL
that points to the API app’s URL.http://localhost:3001
localhost
only works when both apps are run locally using Node. You will need a different value for the environment variable when running in Docker.ps
command to list all processes running, and then the Linux kill
command to kill the two Node.js processes./Challenge-02
folder of their Resources.zip
package. They will use these Dockerfiles in conjunction with the source code in the /Challenge-01
folder for content-web and content-api.NOTE: Before the hack, it is the Coach’s responsibility to download and package up the contents of the /Student/Resources
folder of this hack into a Resources.zip
file. The coach should then provide a copy of the Resources.zip
file to all students at the start of the hack. The student guide refers to relative path locations within this zip package.
If the students get stuck, point them to the ACR documentation for building a container image in Azure:
az acr create -n <name of registry> -g <resource group> --sku Standard
az acr login --name <name of ACR>
az acr repository list --name <name of ACR>