What happens if a container with `--restart=always` keeps crashing immediately upon startup?

Docker uses an exponential backoff strategy. It will restart it instantly, then if it crashes again, wait 100ms, then 200ms, then 400ms, up to a maximum delay (usually 1 minute) to prevent your CPU from being consumed by an infinite crash loop.

How do I forcefully stop a container that is stuck in a restart loop?

You use the standard `docker stop ` or `docker rm -f ` command. Explicitly stopping a container via the CLI tells the Daemon to permanently ignore the restart policy.

Is `--restart=unless-stopped` different from `--restart=always`?

Yes. If you reboot your physical server, `always` will automatically start the container when the server boots up. `unless-stopped` will also do this, EXCEPT if you had manually ran `docker stop` on that container before the server rebooted.

🚀 LEVEL UP TO SENIOR:Unlock 500+ Advanced Practical Challenges & Exercises.

🎓 COURSERA PARTNER:Earn professional Google, Meta, and IBM certificates to supercharge your resume.

Tutorials

HTML MASTER CLASS /// LEARN TAGS /// BUILD STRUCTURE /// SEMANTIC WEB /// HTML MASTER CLASS /// LEARN TAGS ///

⚡ Total XP: 0|💻 dockermasterclass XP: 0

Container Lifecycle

Understand the fundamental state machine of a Docker container. Learn the critical PID 1 rule that governs container lifespan, and master Restart Policies to build self-healing, highly available production architectures.

LOADING ENGINE...