This practical demonstrates Docker Engine verification, daemon architecture understanding, and secure client-server communication using Docker Desktop on Windows. It includes validation of Docker CLI connectivity, context inspection, container execution, and architectural analysis of Docker’s internal communication model.
Docker follows a Client–Server model:
Docker CLI → Docker Daemon → Containers
On Windows, communication happens via:
npipe:////./pipe/docker_engine
Unlike Linux/macOS, direct TCP exposure (port 2375) is restricted by Docker Desktop for security reasons.
docker --version
docker info
docker context ls
If required:
docker context use desktop-linux
Running Containers:
docker ps
All Containers:
docker ps -a
docker images
Docker CLI communicates with daemon using Named Pipe:
docker info
docker ps
Successful execution confirms daemon connectivity.
docker run hello-world
This confirms:
Docker Desktop does not expose TCP 2375 by default due to security risks.
Unsecured TCP exposure can allow:
Modern DevOps environments use:
cd ..
git add .
git commit -m "Added Class Practical 4 Feb - Docker Engine Architecture"
git push
This lab provided in-depth understanding of Docker Engine internals, daemon communication, and secure architecture practices in Windows-based environments. It highlights real-world DevOps considerations when working with container runtimes and remote API configurations.