Run Containers by Using Azure Container Instances

1. Open an incognito or in-private window, and log in to the Azure portal using the username and password provided in the lab environment.
2. From within the portal, initiate the Cloud Shell, and when prompted, select a Bash shell (versus PowerShell).
3. When prompted, choose "Mount a Storage Account."
4. Choose the lab subscription and click Apply.
5. Select the storage account that's already been deployed for you.
6. Select the one, existing, resource group.
7. Create a new fileshare and name it "fileshare" (all lower-case)
8. Click Apply.
9. Wait for the command prompt to appear.

From the Bash command prompt in Cloud Shell:

1. Retrieve the name of the resource group already deployed in the lab environment using the az group list command, and copy the name of the resource group.

2. Set up three variables as follows:

   rg=<SOURCE_GROUP_NAME>
   name=acrlabdemo
   acr="$name$RANDOM"
   

3. Set up a new ACR using the az acr create command. You will need to pass arguments for the resource group, the name of the new ACR, and the service tier, or SKU. Hint: Use the rg and acr environment variables for the first two arguments, and set the SKU to Basic. This step may take several minutes to complete.

4. Enable an admin user for the registry using the az acr update command. You will need to pass arguments for the ACR name (using the acr environment variable) and then set the admin-enabled argument to true.

You should still be in the Cloud Shell session you had opened when creating the ACR instance.

1. Change to the clouddrive directory with cd clouddrive.

2. Create a simple, one-line Dockerfile, called "Dockerfile" with the command, below, which will create the file in your clouddrive directory.

   echo FROM mcr.microsoft.com/hello-world > Dockerfile
   

3. Build (and push) a new imagine in your ACR, using the Dockerfile you just created using the az acr build command. You will need to pass three arguments: the image, the registry name, and the Dockerfile name.

   Hints: The value for the --image argument is sample/hello-world:v1. After the argument for the Dockerfile name, add a space and then a period ("."); the period indicates that the file can be found at the root of the current directory, which is clouddrive. If you leave out the period, you will likely get an error. The build and push will take a few minutes to complete.

4. Close or minimize the Cloud Shell, and return to the resource group overview page in the portal.

5. Find and select the new ACR instance and go to Repositories to confirm that the image exists in the repository.

In the Azure portal, create a new ACI. Ensure that you:

1. Assign it to the existing resource group; do not create a new one.
2. Leave the region defaulted, and name your container anything you wish.
3. Use the image stored in your ACR.

   Hint: Once you select Azure Container Registry for the Image Source, it should default to your ACR and the sample image. If not, see the troubleshooting tips, below.

4. Skip all other tabs in the wizard, and proceed to review and create the ACI. It will take a few minutes to deploy.
5. Go to the resource and select Start. You can monitor the start-up progress in Notifications.
6. When the container has started, navigate to Containers and click Logs to confirm that your installation is working.

Troubleshooting:

• When working through the ACI wizard, if the ACR and image do not appear automatically when you choose Azure Container Registry for the Image Source, you may need to refresh the admin access (which you did at the command line earlier in the lab). To do that in the portal, return to the ACR Overview page, and select Update near the top of the page. Toggle the Admin user to Disabled and Save. Then, toggle the Admin user back to Enabled and Save again. Return to the ACI wizard, and you should see the ACR and the sample image available in the registry and image fields.
• When you start your container in ACI, you may get an error message that says the container is "still transitioning." Wait a couple of minutes and try again.