Actions88
- Container Actions
- Container List
- Container Create
- Container Inspect
- Container Top
- Container Logs
- Container Changes
- Container Export
- Container Stats
- Container Resize
- Container Start
- Container Stop
- Container Restart
- Container Kill
- Container Update
- Container Rename
- Container Pause
- Container Unpause
- Container Attach
- Container Attach Websocket
- Container Wait
- Container Delete
- Container Archive Info
- Container Archive
- Put Container Archive
- Container Prune
- Image Actions
- Network Actions
- Volume Actions
- Swarm Actions
- Node Actions
- Secret Actions
- System Actions
- Exec Actions
- Service Actions
- Task Actions
Overview
This node allows you to update a Docker container by interacting with the Portainer API. It is useful in scenarios where you need to modify container configurations or apply updates programmatically without manually accessing the Docker host or Portainer UI. For example, you can update environment variables, resource limits, or restart policies of a running container as part of an automated workflow.
Properties
| Name | Meaning |
|---|---|
| EndpointID Name or ID | The identifier of the Portainer endpoint to access. You can select from a list of available endpoints or specify an ID using an expression. |
| Id | The ID or name of the Docker container you want to update. |
| Update | The update payload sent as the request body. This should contain the container update details in JSON format. |
Output
The node outputs the JSON response returned by the Portainer API after attempting to update the container. This typically includes the status of the update operation and any relevant metadata about the container post-update.
No binary data output is produced by this node.
Dependencies
- Requires a valid Portainer API URL and an API key credential configured in n8n to authenticate requests.
- Depends on the Portainer API being accessible at the specified endpoint.
- Uses the Portainer API
/api/endpoints/{endpointId}/dockerbase path for Docker operations.
Troubleshooting
- Invalid EndpointID: If the selected endpoint ID is incorrect or inaccessible, the node will fail to connect. Verify the endpoint exists and your credentials have access.
- Container Not Found: Providing an invalid container ID or name will result in an error. Double-check the container identifier.
- Malformed Update Payload: The "Update" property must be a valid JSON string matching the expected schema for container updates. Invalid JSON or missing required fields will cause the API to reject the request.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to perform container updates.
- Network Issues: Connectivity problems between n8n and the Portainer server will cause request failures.