How can I troubleshoot the command execution within the pipeline?

To troubleshoot and understand what is happening during the execution of a particular command, include the following option to enable detailed logging:

docker run --pull=always -e LOG_LEVEL="debug" flyingduckio/duckdefender:latest

In this example, the -e LOG_LEVEL="debug" option is used to enable debug-level logs, which will help identify potential issues.

How can I troubleshoot Docker containers during the cli execution?

To troubleshoot Docker containers, you can use the following commands:

1. Check running containers: To see the list of currently running containers:

   docker ps

2. Check all containers (including stopped ones): This will show you all containers, including those that have stopped:

   docker ps -a

3. View container logs: To check the logs of a specific container, use the container ID or name:

   docker logs <container_id_or_name>

4. Default Docker container logs file path: Docker stores container logs in the following location on the host:

   /var/lib/docker/containers/<container_id>/<container_id>-json.log

By using these commands, you can effectively troubleshoot issues with Docker containers.