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
Container → Start
AI-generatedOverview
This node operation starts a stopped Docker container within a specified environment in Portainer. It is useful for automating container lifecycle management, such as restarting containers after maintenance or scaling operations.
Use Case Examples
- Starting a specific container by its ID in a given environment to resume its operation.
- Automating container start as part of a deployment pipeline.
Properties
| Name | Meaning |
|---|---|
| Environment ID | The ID of the environment/endpoint in Portainer where the container resides. |
| Container ID | The unique identifier of the container to start. |
| Request Options | Additional HTTP request options such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
body- The JSON response body from the Portainer API after starting the container, typically empty or status confirmation.
Dependencies
- Requires Portainer API access with an API key credential.
Troubleshooting
- Ensure the Environment ID and Container ID are correct and the container is in a stopped state before starting.
- Check API key permissions to allow container start operations.
- If SSL issues occur, consider enabling 'Ignore SSL Issues' option or verify the SSL certificate.
- Timeout errors may require increasing the timeout setting in request options.
Links
- Portainer API - Start Container - Official Portainer API documentation for starting a Docker container.