Utilities
Wrap a container-only tool as a workflow step
Execute a custom shell script inside one or more Docker images.
Shell
overview
What docker-exec-sh does
docker-exec-sh takes an image-list and a script-to-be-executed file, runs that script inside each image, and collects whatever it writes into a FOLDER.
Reach for it when a tool ships only as a container and has no dedicated node. The script owns the behavior: install, scan, transform, or chain commands in the image environment.
One image-list can fan the same script across multiple images, useful for comparing tool versions or checking a set of base images in a single pass.
use cases
Where docker-exec-sh fits
Wrap a container-only tool as a node
Point the script at an image's binary and run it in place, so a tool that ships only as a Docker image becomes a reusable workflow step with folder output.
Run one script across many images
Feed an image-list to run the same script against each image, handy for comparing tool versions or checking a set of base images in a single pass.
Chain a container tool into recon or scanning
Run a container-only scanner or parser mid-workflow and hand its output folder to the next node, with no rebuild of that tool as a native node.
Prototype before building a native node
Test a tool's command line inside its own image first, then promote it to a dedicated node once the workflow shape has settled.
reference
docker-exec-sh inputs and flags
| Name | Type | Flag | Description |
|---|---|---|---|
| image-list | FILE | · | List of Docker images, one per line, where the script runs. |
| script-to-be-executed | FILE | · | Shell script executed inside each image from the list. |
Showing key inputs. docker-exec-sh exposes 2 inputs in total.
example
Run docker-exec-sh
# docker-exec-sh runs script-to-be-executed inside each image in image-list
# image-list: trickest/nuclei:latest
# script-to-be-executed:
nuclei -u https://example.com -severity critical,high -o /output/findings.txt[docker-exec-sh] image-list: 2 images
[docker-exec-sh] trickest/httpx:latest -> running script
https://example.com [200] [Example Domain] [nginx]
https://staging.example.com [200] [Staging] [nginx]
[docker-exec-sh] trickest/httpx:v1.6.0 -> running script
https://example.com [200] [Example Domain] [nginx]
[docker-exec-sh] collected output/ (2 images, exit 0)guidance
Choosing docker-exec-sh
Use docker-exec-sh when the tool you need ships as a Docker image and has no native node. Write the script, list the image, and collect the FOLDER output. Prefer a dedicated node when one already exists for cleaner inputs and outputs.
assert-tool
Utilities helper for workflow checks. docker-exec-sh runs an arbitrary container command, not a check.
anew
Stream utility for deduplicating lines. Sibling utility for a narrower job.
faq
docker-exec-sh questions
related
More Utilities tools
browser-fetch
Headless Chromium render: requested URL, final URL, status, and title next to the page.
cewl
Spider a URL and return a wordlist for password crackers.
csvkit
SQL on one CSV. The table name is the file stem.
dnsgen
Wordlist and mined-word subdomain permutation.
duckdb
In-process SQL on CSV, JSON, and Parquet. No server.
edge-tts
Microsoft Edge neural speech from text or a script file. No API key.
Run docker-exec-sh yourself
An image list and a script feed docker-exec-sh, which runs the script inside each image and writes the collected output as a queryable folder.
Facts on this page come from the live Trickest tool library.