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
This node integrates with the Portainer API to manage Docker images and other Docker-related resources. Specifically, the Image - Push operation allows users to push a Docker image from a specified environment (endpoint) to a Docker registry.
Typical use cases include:
- Automating the deployment pipeline by pushing newly built or tagged Docker images to a remote registry.
- Managing Docker images across multiple environments/endpoints via Portainer.
- Integrating Docker image management into broader workflows in n8n.
For example, after building a Docker image in a CI/CD workflow, this node can push that image to a registry for distribution or deployment.
Properties
| Name | Meaning |
|---|---|
| Environment ID | The ID of the Portainer environment/endpoint where the Docker image resides. |
| Image ID | The unique identifier of the Docker image to be pushed. |
| Image Tag | The tag of the image to push (e.g., "latest"). Defaults to "latest". |
Output
The node outputs JSON data representing the response from the Portainer API after attempting to push the image. This typically includes status information about the push operation, such as success confirmation or error details.
No binary data output is involved in this operation.
Dependencies
- Requires an active Portainer instance accessible via its API.
- Requires an API key credential configured in n8n to authenticate requests to the Portainer API.
- The node uses the base URL and API key from the configured credentials to make HTTP requests.
Troubleshooting
Common issues:
- Incorrect
Environment IDorImage IDwill cause the API call to fail because the resource cannot be found. - Insufficient permissions or invalid API key may result in authentication errors.
- Network connectivity issues to the Portainer API endpoint can cause request failures.
- Incorrect
Error messages:
- Authentication errors usually indicate invalid or missing API key credentials.
- "Not Found" errors suggest incorrect environment or image IDs.
- Timeout or connection errors imply network problems or unreachable Portainer server.
Resolutions:
- Verify the correctness of the Environment ID and Image ID parameters.
- Ensure the API key credential is valid and has sufficient permissions.
- Confirm network access to the Portainer API endpoint.
Links and References
This summary is based solely on static analysis of the provided source code and property definitions.