From 77cfeacf601eb5b017465ddbecc287762a4f7845 Mon Sep 17 00:00:00 2001 From: Iker Pedrosa Date: Tue, 26 Aug 2025 12:35:06 +0200 Subject: [PATCH] doc/contributions/build_install.md: container troubleshooting Extend the container section to document the container troubleshooting. Signed-off-by: Iker Pedrosa --- doc/contributions/build_install.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/doc/contributions/build_install.md b/doc/contributions/build_install.md index 610b1bc4e..a08629477 100644 --- a/doc/contributions/build_install.md +++ b/doc/contributions/build_install.md @@ -73,3 +73,31 @@ were running some of the CI checks locally: ``` share/container-build.sh ``` + +### Container troubleshooting + +When working with containers for testing or development, +you may encounter issues. +Here are common troubleshooting steps: + +**Post-test inspection:** +- **Container persistence**: After tests complete, containers are left running + to allow inspection of the test environment and debugging of any failures. + This enables you to examine logs, file states, and system configuration + that existed when tests ran. + +**Container management:** +- **List containers**: `docker ps -a` to see all containers and their status. +- **Access container**: `docker exec -it bash` to get shell access. +- **Container logs**: `docker logs ` to view container output. +- **Remove containers**: `docker rm ` to clean up stopped containers. + +**Common issues:** +- **Container not found**: ensure you've run the Ansible playbook + to create the required containers. +- **Permission issues**: verify the container has proper privileges + for user/group operations. +- **Network connectivity**: check that containers can communicate + if tests involve network operations. +- **Resource constraints**: ensure sufficient disk space and memory + for container operations. -- 2.47.3