Rolling Updates
Rolling updates enable the platform to seamlessly update your application by starting a new container and gracefully stopping the currently running one. This approach minimizes downtime and ensures your service remains available during updates.
How Rolling Updates Work
When a new update is initiated, a new container instance is launched while the existing container continues running. Once the new container is confirmed healthy, the old container is stopped.
Conditions for Rolling Updates
For rolling updates to function properly:
- Health Check Configuration — A valid health check must be configured and passing. Without a proper health check, the rolling update cannot verify the container's readiness.
- Default Container Naming — Rolling updates require the default container naming convention. Custom container names may prevent correct instance management.
- Not Docker Compose — Rolling updates are not supported on Docker Compose-based deployments.
- No Port Mapping — If a port is mapped to the host, the new container cannot bind to the same port during the update process.
Configuring Health Checks
Ensure your application includes a health check endpoint that returns a successful response (e.g., HTTP 200). See our Health Check Guide for details.
Troubleshooting Rolling Updates
- Verify Health Check Configuration — Ensure your health check endpoint works and returns a valid response.
- Review Container Naming — Confirm default container naming is used.
- Check Logs — Review proxy or application container logs for error messages.