Diagnosing a Broken Container

In this exercise, you will take on the role of a DevOps engineer tasked with diagnosing and fixing a Docker container that fails to start or behave as expected. This exercise will help you enhance your troubleshooting skills, which are crucial for maintaining stable and reliable applications in production environments.

Requirements

We are using the same todo app from previous exercises and some intern did some changes which is resulting in broken container. The container has been published to the repository. Your task is to identify the issues causing the container to fail and resolve them.

Please complete previous exercises before proceeding. It uses the same application and you might need to run the container of that application.

To successfully complete this exercise, you need to:

• Pull the provided Docker image from Docker Hub. The link is present below in Resources section.
• Attempt to run the container and observe the failure.
• Diagnose the problem by inspecting logs, environment configurations, etc.
• Correct the problems and run the container successfully.

Resources

• Docker Logs
• Inspecting Containers
• Troubleshooting Docker Containers
• Broken docker image to use: tdevsin/broken-todo-app

Acceptance Criteria

1. Docker Image Pulled: You must pull the provided Docker image from Docker Hub.
2. Issue Identified: Correctly identify the issue(s) causing the container to fail.
3. Container Runs: The container must run successfully after the necessary fixes are applied.
4. Explanation Provided: Provide a clear explanation of the issue and the steps you took to fix it.

Possible Ways to Implement

1. Pull the Docker Image: Start by pulling the provided Docker image using the following command:

   docker pull tdevsin/broken-todo-app
   

2. Run the Container: Attempt to run the container. Note that the container is expected to fail.

3. Check the Logs: Use the docker logs command to inspect the container's output and identify any error messages. Carefully look at the logs, you may find something.

4. Inspect the Container: Use docker inspect to review the container’s settings and configurations.