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 → Tag
AI-generatedOverview
This node operation allows users to create a new tag for an existing Docker image within a specified environment in Portainer. It is useful for managing image versions and organizing images in repositories by tagging them appropriately.
Use Case Examples
- Tagging an image 'abc123def456' in environment '1' with a new tag 'v2.0' under the repository 'myrepo' to mark a new version release.
- Organizing images by tagging them with environment-specific or deployment-specific tags for easier identification and deployment management.
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 tagged. |
| Repository | The repository name under which the new tag will be created. |
| New Tag | The new tag name to assign to the image. |
Output
JSON
response- The response from the Portainer API after tagging the image, typically confirming the tag creation.
Dependencies
- Portainer API with an API key credential for authentication
Troubleshooting
- Ensure the Environment ID and Image ID are correct and exist in Portainer to avoid 'not found' errors.
- Verify that the repository name and new tag are valid and conform to Docker image tagging conventions.
- Check API key credentials and network connectivity to Portainer to prevent authentication or connection errors.
Links
- Portainer API - Tag Image - Official Portainer API documentation for tagging Docker images.