Actions72
- Image Actions
- Config Actions
- Container Actions
- Edge Group Actions
- Edge Stack Actions
- Network Actions
- Node Actions
- Registry Actions
- Secret Actions
- Service Actions
- Stack Actions
- Team Actions
- Template Actions
- User Actions
- Volume Actions
- Webhook 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 management of container image registries that your Docker environments use, such as adding new private or public registries for pulling images.
Practical scenarios include:
- Automatically adding a new private registry when onboarding a new project.
- Managing multiple registry types (e.g., Quay.io, Azure, Gitlab, DockerHub) centrally via automation workflows.
- Updating registry credentials programmatically to maintain secure access.
Properties
| Name | Meaning |
|---|---|
| Registry Name | The name identifier for the registry being 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 authenticating with the registry. |
| Password | Optional password for authenticating 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 connection to a Portainer instance with API access.
- Requires an API key credential configured in n8n to authenticate requests to Portainer.
- The base URL of the Portainer API must be set in the credentials.
Troubleshooting
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions to create registries.
- Invalid input: Missing required fields like Registry Name or Registry URL will cause errors. Double-check all required properties are provided.
- Unsupported registry type: Use one of the predefined registry types; custom values may not be accepted.
- Network issues: Verify connectivity to the Portainer API endpoint.
- API errors: If Portainer returns an error, check the message for clues (e.g., duplicate registry name).