Bird
0
0

You set a health check command but Docker always shows the status as 'starting'. What could be wrong?

medium📝 Troubleshoot Q7 of 15
Docker - Logging and Monitoring
You set a health check command but Docker always shows the status as 'starting'. What could be wrong?
AThe container image is corrupted
BThe container has no network access
CThe Docker daemon is not running
DThe health check command takes longer than the start period
Step-by-Step Solution
Solution:

  1. Step 1: Understand 'starting' health status meaning

    'Starting' means health check is still within the initial grace period.

  2. Step 2: Identify cause for prolonged 'starting' status

    If health check command takes too long, Docker keeps status as 'starting'.

  3. Final Answer:

    The health check command takes longer than the start period -> Option D

  4. Quick Check:

    Long health check duration = 'starting' status [OK]
Quick Trick: Health check must finish within start period to avoid 'starting' [OK]
Common Mistakes:
  • Assuming network issues cause 'starting' status
  • Thinking Docker daemon status affects health check state

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Docker Quizzes
Docker Security - Capabilities and privilege control - Quiz 8hard Docker Security - Read-only filesystem containers - Quiz 13medium Docker Swarm - Swarm mode initialization - Quiz 5medium Docker in CI/CD - Running tests in containers - Quiz 7medium Docker in CI/CD - Deploying from CI/CD pipeline - Quiz 14medium Docker in CI/CD - GitLab CI with Docker - Quiz 11easy Image Optimization - Why image optimization matters - Quiz 11easy Image Optimization - Reducing image size strategies - Quiz 15hard Production Patterns - Sidecar container pattern - Quiz 15hard Resource Management - Resource monitoring per container - Quiz 13medium