Maintenance & Recovery
Update Containers
Update one application deliberately, verify it, and retain a route back when an image breaks.
Guide difficulty⭐⭐⭐⭐⭐ Beginner Friendly
Estimated time⏱️ Around 20–40 minutesEstimated for a first-time user.
Why not update everything blindly?
A newer image can change environment variables, database versions or network behaviour. Updating one stack at a time makes failures understandable.
Read the release notes
Check for breaking changes and required migrations.
Back up configuration
Copy the application’s persistent config before pulling the new image.
Update only that service or stack
Do not restart unrelated working services.
Test its complete job
Opening the dashboard is not enough; test the function that matters.
Record the version
Update the project notes once the new version is proven.
IMAGE PLACEHOLDERTerminal showing a targeted Docker Compose pull and recreation of one service.