Docker icon

Docker

Interact with Docker
Join our community

Actions15

Overview

This node allows interaction with Docker resources directly from n8n workflows. Specifically, for the Network - Get operation, it retrieves detailed information about a specific Docker network by its ID. This is useful in scenarios where you need to programmatically inspect Docker networks, such as verifying network configurations, monitoring network status, or integrating Docker network data into automation pipelines.

Practical examples include:

  • Fetching details of a Docker network before deploying containers that depend on it.
  • Auditing network settings as part of a CI/CD pipeline.
  • Triggering alerts or actions based on network properties or existence.

Properties

Name Meaning
ID The unique identifier of the Docker network to retrieve. This should be provided as a string representing the network's ID.

Output

The node outputs JSON data containing the detailed information of the requested Docker network. The structure corresponds to the Docker API response for a network inspection, typically including fields such as network ID, name, driver type, scope, connected containers, IPAM configuration, and other metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires a valid Docker API connection configured via credentials that provide access to the Docker daemon.
  • The node depends on the dockerode library to communicate with the Docker API.
  • Proper permissions and network access to the Docker host are necessary.

Troubleshooting

  • No credentials got returned!
    This error indicates missing or misconfigured Docker API credentials. Ensure that the Docker credentials are properly set up in n8n and linked to the node.

  • Invalid or empty ID parameter
    If the ID property is not provided or incorrect, the Docker API call will fail. Verify that the network ID is correct and exists on the Docker host.

  • Docker API connectivity issues
    Network problems or insufficient permissions can cause failures. Confirm that the Docker daemon is accessible from the n8n environment and that the credentials have appropriate rights.

Links and References

Discussion