Running containers is just the beginning. In real-world scenarios, you will often need to peek inside the running containers to debug issues, inspect files, or execute additional commands. This is where the docker exec command becomes your best friend for container troubleshooting and exploration.

In this challenge, a Python API server is already running in a container called app-1. The application serves its main endpoints on 0.0.0.0:8080 but also opens a special debugging interface on 127.0.0.1:9000/debug. Since the debugging port is opened on localhost, it can only be accessed from within the container.

Your mission is to:

1. Start an interactive shell inside the running app-1 container.
2. Query the debugging endpoint to inspect the application's state.

Good luck!

Hint 1: Starting an interactive shell 💡

The docker exec command allows you to execute arbitrary commands inside a running container. To start an interactive shell session, you typically need to:

• Use the -i flag for interactive mode
• Use the -t flag to allocate a pseudo-TTY
• Specify the container name or ID
• Specify the shell to run (like bash or sh)

Try running docker exec --help to see the exact syntax or check this tutorial for more details.

apt update && apt install -y curl