All 15 Docker & Deployment questions
More in Docker & Deployment
What is a multi-stage Docker build, and why is it commonly used for Node.js applications? What is the difference between the CMD and ENTRYPOINT instructions in a Dockerfile for a Node.js application? How does Docker Compose simplify local development for a Node.js application that depends on a database and a cache? What is a .env file, and how does it interact with a Dockerized Node.js application's configuration? How do Kubernetes ConfigMaps and Secrets differ, and how are they typically consumed by a Node.js pod? What is the purpose of setting explicit CPU and memory resource requests and limits for a Node.js container in Kubernetes? How do you properly handle process signals (SIGTERM) inside a containerized Node.js application to support graceful shutdown? Why should a Node.js Docker container generally run as a non-root user, and how do you configure this in a Dockerfile? How would you optimize Docker layer caching in a Node.js Dockerfile to speed up repeated builds during development? What is the difference between deploying a Node.js application to a Platform-as-a-Service (like Heroku or Render) versus a self-managed container orchestrator (like Kubernetes)?
Advertisement
Node.js › Docker & Deployment

What is the purpose of a HEALTHCHECK instruction in a Dockerfile for a Node.js application?

Intermediate

Answer

HEALTHCHECK defines a command Docker periodically runs inside the container to determine if the application is actually functioning correctly, not just whether the process is technically still running -- Docker (and orchestrators reading this status) can use a failing health check to automatically restart an unhealthy container or avoid routing traffic to it, providing an additional layer of self-healing beyond simply checking if the process exists.
HEALTHCHECK --interval=30s --timeout=3s --retries=3 \
  CMD node healthcheck.js || exit 1

// healthcheck.js: makes a request to the app's own /health endpoint
// and exits with a non-zero code if it doesn't respond successfully
Real-world example A container that had technically stayed 'running' while its underlying HTTP server had silently crashed internally (leaving only a zombie process) is caught by a HEALTHCHECK that actively probes the /health endpoint, letting Docker detect and restart the actually-unhealthy container.

Common follow-ups: How does a Dockerfile-level HEALTHCHECK relate to and differ from Kubernetes's own separate liveness/readiness probes?;What happens to a container marked 'unhealthy' by Docker if nothing is configured to act on that status?

Cloud & DevOps;Deployment & Process Managers (PM2)
All 15 Docker & Deployment questions