Docker icon

Docker

Interact with Docker

Actions15

Network → Get

AI-generated

Overview

This n8n node allows you to interact with Docker resources. Specifically, when configured for the Network resource and the Get operation, it retrieves detailed information about a specific Docker network by its ID. This is useful in automation scenarios where you need to inspect or process metadata about Docker networks as part of your workflow.

Practical examples:

  • Fetching details of a Docker network to verify its configuration before deploying containers.
  • Auditing network settings across multiple Docker hosts.
  • Integrating Docker network data into monitoring or reporting workflows.

Properties

Name Meaning
ID The unique identifier of the Docker network you want to retrieve information about.

Output

The output is a JSON object containing the details of the specified Docker network. The structure typically includes fields such as:

{
  "Name": "network_name",
  "Id": "network_id",
  "Created": "timestamp",
  "Scope": "local",
  "Driver": "bridge",
  "EnableIPv6": false,
  "IPAM": { /* IP address management config */ },
  "Containers": { /* attached containers info */ },
  "Options": { /* driver options */ },
  // ...other Docker network properties
}

Note: The exact fields depend on the Docker API response.

Dependencies

  • Docker Engine API: The node requires access to a Docker host via the Docker API.
  • Credentials: You must configure dockerCredentialsApi in n8n to connect to your Docker instance.

Troubleshooting

  • Missing Credentials:
    Error: No credentials got returned!
    Solution: Ensure that valid Docker credentials are set up in n8n and assigned to this node.

  • Invalid Network ID:
    If an invalid or non-existent network ID is provided, the node may return an error from the Docker API.
    Solution: Double-check the network ID for typos or ensure the network exists.

  • Connection Issues:
    Errors related to connecting to the Docker daemon (e.g., permission denied, connection refused).
    Solution: Verify that the Docker host is reachable from the n8n instance and that credentials have sufficient permissions.

Links and References

Discussion