Actions86
- Config Actions
- Container Actions
- Edge Group Actions
- Edge Stack Actions
- Environment Actions
- Image Actions
- Network Actions
- Node Actions
- Registry Actions
- Secret Actions
- Service Actions
- Setting Actions
- Stack Actions
- System Actions
- Team Actions
- Template Actions
- User Actions
- Volume Actions
- Webhook Actions
Image → Push
AI-generatedOverview
This node operation allows users to push a Docker image to a registry using the Portainer API. It is useful for scenarios where you need to upload a locally built or tagged Docker image to a remote container registry for distribution or deployment.
Use Case Examples
- Pushing a Docker image with a specific tag to a private registry.
- Automating the deployment pipeline by pushing images to a registry after a successful build.
Properties
| Name | Meaning |
|---|---|
| Environment ID | The ID of the environment/endpoint in Portainer where the image resides. |
| Image ID | The ID of the Docker image to be pushed. |
| Image Tag | The tag of the image to push, defaults to 'latest' if not specified. |
| Request Options | Additional request options such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
body- The response body from the Portainer API after pushing the image, typically containing status or result information.
Dependencies
- Requires an API key credential for authenticating with the Portainer API.
Troubleshooting
- Ensure the Environment ID and Image ID are correct and correspond to existing resources in Portainer.
- Verify that the API key credential has sufficient permissions to push images to the registry.
- Check network connectivity and proxy settings if the push operation fails due to connection issues.
- If SSL errors occur, consider enabling the option to ignore SSL certificate validation, but be aware of security implications.
Links
- Portainer API - Push an Image - Official Portainer API documentation for pushing Docker images to a registry.