Actions72
- Image Actions
- Network Actions
- Node Actions
- Registry Actions
- Secret Actions
- Service Actions
- Stack Actions
- Team Actions
- Template Actions
- User Actions
- Volume Actions
- Webhook Actions
- Config Actions
- Container Actions
- Edge Group Actions
- Edge Stack Actions
Overview
The node integrates with the Portainer API to manage Docker environments, specifically allowing inspection of Docker containers. The "Inspect" operation for the "Container" resource retrieves detailed information about a specific container within a given environment (endpoint). This is useful for obtaining comprehensive metadata and configuration details about a container, such as its state, network settings, volumes, image, and runtime parameters.
Practical scenarios include:
- Debugging container issues by examining container configuration and status.
- Auditing container properties in automated workflows.
- Integrating container inspection data into monitoring or reporting systems.
Properties
| Name | Meaning |
|---|---|
| Environment ID | The ID of the Portainer environment/endpoint where the container resides. |
| Container ID | The unique identifier of the Docker container to inspect. |
Output
The node outputs JSON data representing the full inspection details of the specified container. This includes all metadata returned by the Portainer API's container inspection endpoint, such as container configuration, state, network settings, mounts, and other runtime information.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Portainer API.
- The node must be configured with the base URL of the Portainer instance.
- The target environment (endpoint) must exist and be accessible via Portainer.
Troubleshooting
- Invalid Environment ID or Container ID: If the IDs are incorrect or the container does not exist, the API will return an error. Verify that the environment and container IDs are correct.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to access the container details.
- Network Issues: Connectivity problems between n8n and the Portainer server can cause request failures.
- API Rate Limits or Timeouts: Large container inspection responses might time out; consider network stability and API limits.