Actions12
Overview
This node interacts with Docker to run containers based on user-specified parameters. It allows users to specify the Docker image, command to execute inside the container, volume mounts for persistent or shared storage, and the working directory within the container. This node is useful for automating containerized workflows, running isolated tasks, or testing applications in a controlled environment.
Use Case Examples
- Running a container with a specific image and command to perform a batch job.
- Mounting host directories or Docker volumes into the container to share data between the host and container.
- Setting a working directory inside the container to control where commands execute.
Properties
| Name | Meaning |
|---|---|
| Image | The Docker image to use for running the container. |
| Command | The command to execute inside the container, specified as a JSON array. |
| Volume Mounts | Host directories or Docker volumes to mount inside the container, including host path, container path, and read-only flag. |
| Working Directory | Working directory inside the container where commands will execute. |
Output
JSON
stdout- Standard output from the container run command.stderr- Standard error output from the container run command.
Dependencies
- Docker daemon accessible via Docker API
- An API key credential for Docker authentication
Troubleshooting
- Ensure Docker daemon is running and accessible from the environment where the node executes.
- Verify that the Docker image name is correct and accessible (public or private registry).
- Command must be a valid JSON array; otherwise, an error is thrown.
- Volume mounts require both host path and container path to be specified; missing either will cause an error.
- Check permissions for volume mounts, especially if mounting host directories as read-only.
- Common error: 'No credentials got returned!' indicates missing or invalid Docker API credentials.