Docker basics
Check the Docker engine, inspect containers and understand where lab services run.
Where the lab runs
Portal manages lab services through Docker on its configured host. Your browser displays Portal and the service interfaces; the Docker host provides the compute, storage and networking.
Docker networks and published service ports determine how tools reach an environment. Containerization alone does not define the isolation boundary. Use a separate lab environment and configure the connections you need.
Check the engine
docker version
docker compose version
docker infoThe server section of docker version confirms that the CLI can reach the engine. On Docker Desktop, confirm that the application has finished starting and is using Linux containers.
Inspect containers and resources
docker ps -a
docker stats --no-stream
docker system dfUse docker ps -a to see running and stopped containers. Resource statistics help identify memory pressure; disk usage shows whether image downloads or lab data may be running out of space.
Run docker compose commands from the folder containing the Compose file you intend to inspect. The Portal installation and a loaded lab are different Compose projects.
