Difficulty: intermediate
Estimated Time: 45-60 minutes

BoxBoat Logo

Docker Debugging

Docker Compose is an extremely important tool for local development. Debugging is one of the hardest things about Docker. There are many different components (containers, configuration, images, networks, volumes) that can go wrong, and that doesn't include the actual application.

In this lab, we'll go through several different exercises to help get debugging experience.

Please email feedback to: [email protected]

Debugging is one of the hardest things about Docker. Even after using it for years, some things are just difficult. For this final lab, we'll use these debugging skills to fix an application that has many errors.

Debugging

Step 1 of 3

Docker CLI

Docker CLI

The Docker CLI lets us start and configure containers, in addition to all other aspects of the system, including networking and volumes. We'll work through these activities together.

Docker Container Run

First, help me modify these commands so they will all execute successfully:

  1. docker container run -d -p 8080:80 --name nginx nginx
  2. docker container run -d -p 8081:80 --name nginx nginx
  3. docker container run -d -p 8082:80 --name nginx nginx

Next, let's get these commands working:

  1. docker container run -d -p 8080:80 --name nginx nginx
  2. docker container run -d -p 8080:80 --name tomcat tomcat

Next, let's get these commands working:

  1. docker container run -v my-vol:/root/app -d -p 8080:80 --name nginx
  2. docker container run -n my-net -d -p 8081:80 --name nginx

Finally, let's get this command working:

  1. docker container run -d -p 10080:8080 --name mario boxboat/hextris