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 "Registry - Get" operation retrieves detailed information about a specific Docker image registry by its ID. This is useful when you want to fetch configuration or status details of a particular registry that your Docker environment uses for storing and distributing container images.
Common scenarios include:
- Auditing or verifying registry configurations.
- Fetching registry details before performing updates or deletions.
- Integrating registry data into automation workflows for monitoring or reporting.
Example: You have multiple Docker registries configured in Portainer and want to retrieve the details of one registry (e.g., its URL, type, credentials) to display or use in subsequent workflow steps.
Properties
| Name | Meaning |
|---|---|
| Registry ID | The unique identifier of the registry to retrieve. This is required to specify which registry's details to fetch. |
Output
The node outputs JSON data representing the full details of the specified registry as returned by the Portainer API. This typically includes fields such as:
- Registry ID
- Name
- URL
- Type (e.g., DockerHub, Azure, Custom)
- Username (if applicable)
- Other metadata related to the registry configuration
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to a Portainer instance via its API.
- Requires an API key credential for authenticating requests to the Portainer API.
- The base URL of the Portainer API must be configured in the node credentials.
Troubleshooting
- Invalid Registry ID: If the provided Registry ID does not exist or is incorrect, the API will return an error indicating the resource was not found. Verify the Registry ID is correct.
- Authentication Errors: If the API key is missing, invalid, or lacks permissions, authentication errors will occur. Ensure the API key credential is correctly set up and has sufficient rights.
- Network Issues: Connectivity problems to the Portainer API endpoint can cause request failures. Check network access and the correctness of the base URL.
- API Version Mismatch: Using an incompatible Portainer API version may cause unexpected errors. Confirm compatibility between the node and your Portainer server version.