step-security/Docker Container Logs Collection
Automatically collect and manage logs from all running Docker containers in your GitHub Actions workflow
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| dest | Destination folder path for log files. When specified, creates individual log files for each container named after the container (e.g., 'redis.log', 'postgres.log'). If not provided, all logs are streamed to stdout for immediate viewing. The directory will be created automatically if it doesn't exist. | no | — |
| images | Comma-separated list of Docker image names to filter containers. Supports both exact matches with tags (e.g., "mongo:3.4.22") and name-only matches without tags (e.g., "mongo" matches "mongo:3.4.22"). If not specified, logs from all running containers will be collected. Example: "redis,postgres,nginx" | no | — |
| tail | Maximum number of log lines to collect from each container. Use "all" to collect complete logs or specify a number (e.g., "100", "500"). Helpful for limiting output size in workflows with verbose logging. | no | all |
| shell | Shell interpreter to use for executing Docker commands. Defaults to "/bin/sh" for maximum compatibility across different environments. Can be changed to "/bin/bash" or other shells as needed. | no | /bin/sh |
Outputs
no outputs