Actions15
Overview
This n8n node allows you to interact with Docker resources. Specifically, when configured for the Volume resource and the Get operation, it retrieves detailed information about a specific Docker volume by its ID. This is useful in automation scenarios where you need to inspect or process metadata about Docker volumes as part of your workflow.
Practical examples:
- Automatically fetch details of a backup volume before performing maintenance.
- Integrate with monitoring tools to check properties of a specific Docker volume.
- Use in workflows that require validation or reporting on storage usage.
Properties
Name | Meaning |
---|---|
ID | The unique identifier (name) of the Docker volume to retrieve information about. |
Output
The output is a JSON object containing the details of the specified Docker volume. Typical fields may include:
{
"Name": "my_volume",
"Driver": "local",
"Mountpoint": "/var/lib/docker/volumes/my_volume/_data",
"Labels": {},
"Scope": "local",
"Options": {},
"CreatedAt": "2024-06-01T12:34:56Z"
}
- The exact structure depends on the Docker API response, but generally includes metadata such as name, driver, mount point, labels, options, and creation time.
Dependencies
- Docker Engine: The node requires access to a running Docker daemon.
- Credentials: You must configure Docker credentials in n8n (
dockerCredentialsApi
). - External Library: Uses the
dockerode
npm package for Docker API communication.
Troubleshooting
No credentials got returned!
Error message: "No credentials got returned!"
Resolution: Ensure that Docker credentials are properly set up in n8n and assigned to this node.Invalid Volume ID
If the provided ID does not correspond to an existing Docker volume, the node will return an error from the Docker API.
Resolution: Double-check the volume ID for typos or existence.Docker Daemon Unreachable
If the Docker service is not running or network settings are incorrect, connection errors may occur.
Resolution: Verify Docker is running and credentials are correct.