Skip to content

Latest commit

 

History

History
60 lines (46 loc) · 3.15 KB

01a-containers.md

File metadata and controls

60 lines (46 loc) · 3.15 KB
Raw

Challenge 1, Path A: Got Containers?

< Previous Challenge - Home - Next Challenge >

Introduction

The first step in our journey will be to take our application and package it as a container image using Docker.

Description

In this challenge we'll be creating an Azure Linux VM, building, and running the node.js based FabMedical app on the VM to see it working. Then we'll be creating Dockerfiles to build a container image of the application.

  • Deploy an Azure VM using provided ARM Template and parameters file in the "Files" tab of the Team's General channel.

    • The template deployment will ask you to provide an admin password for the VM. The 12-character password must meet 3 out of 4 of these criteria:

      • Have lower characters
      • Have upper characters
      • Have a digit
      • Have a special character

    • NOTE: To ssh into the build machine using port 2266 on the VMs public IP:

      • ssh -p 2266 wthadmin@<VM Public IP>
      • Verify that docker and Azure CLI are installed on the VM.

  • Run the node.js application

    • Each part of the app (api and web) runs independently.
    • Build the API app by navigating to the content-api folder and run npm install.
    • To start the app, run node ./server.js &
    • Verify the API app runs by hitting its URL with one of the three function names. Eg: http://localhost:3001/speakers

  • Repeat for the steps above for the content-web app, but verify it's available via a browser on the Internet!

    • NOTE: The content-web app expects an environment variable named CONTENT_API_URL that points to the API app's URL.

  • Create a Dockerfile for the content-api app that will:

    • Create a container based on the node:8 container image
    • Build the Node application like you did above (Hint: npm install)
    • Exposes the needed port
    • Starts the node application

  • Create a Dockerfile for the content-web app that will:

    • Do the same as the Dockerfile for the content-api
    • Also sets the environment variable value as above

  • Build Docker images for both content-api and content-web

  • Run both containers you just built and verify that it is working.

    • Hint: Run the containers in 'detached' mode so that they run in the background.
    • NOTE: The containers need to run in the same network to talk to each other.
      • Create a Docker network named "fabmedical"
      • Run each container using the "fabmedical" network
      • Hint: Each container you run needs to have a "name" on the fabmedical network and this is how you access it from other containers on that network.
      • Hint: You can run your containers in "detached" mode so that the running container does NOT block your command prompt.

Success Criteria

  1. You can run both the node.js based web and api parts of the FabMedical app on the VM
  2. You have created 2 Dockerfiles files and created a container image for both web and api.
  3. You can run the application using containers.

Learning Resources