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 registries. Specifically, the "Create" operation under the "Registry" resource allows users to create a new Docker image registry within Portainer. This is useful for automating the addition of registries where Docker images are stored, enabling subsequent operations like pulling or pushing images through Portainer-managed environments.
Practical scenarios include:
- Automating infrastructure setup by programmatically adding private or public registries.
- Integrating with CI/CD pipelines to dynamically register new image sources.
- Managing multiple registry types (e.g., Quay.io, Azure, DockerHub) centrally via Portainer.
Properties
| Name | Meaning |
|---|---|
| Registry Name | The name identifier for the registry to be created. |
| Registry URL | The URL endpoint of the registry. |
| Registry Type | The type of registry. Options: Quay.io, Azure, Custom, Gitlab, ProGet, DockerHub, ECR. |
| Username | Optional username for authentication with the registry. |
| Password | Optional password for authentication with the registry. |
Output
The node outputs the JSON response from the Portainer API after creating the registry. This typically includes details about the newly created registry such as its ID, name, URL, type, and possibly status or metadata returned by Portainer.
No binary data output is involved in this operation.
Dependencies
- Requires an active Portainer API instance accessible via a base URL.
- Requires an API key credential configured in n8n to authenticate requests to Portainer.
- The node uses HTTP POST requests to the
/registriesendpoint of the Portainer API.
Troubleshooting
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions to create registries.
- Invalid input data: Verify that required fields (Registry Name, Registry URL, Registry Type) are correctly provided and formatted.
- Network issues: Confirm that the Portainer API endpoint is reachable from the n8n environment.
- API errors: If the registry type value is invalid or unsupported, the API may reject the request; use one of the predefined registry types.
- Empty username/password: If the registry requires authentication, provide valid credentials; otherwise, leave these fields empty.