localstack.system.up

Service availability

Dimensions:None

Technical Annotations (32)

Configuration Parameters (4)

healthcheck.timeoutrecommended: 10s

Doubled from default 5s to accommodate slower health check responses

healthcheck.start_periodrecommended: 15s

Grace period for container initialization before health checks count toward failure

healthcheck.intervalrecommended: 10s

Time between consecutive health checks

healthcheck.retriesrecommended: 3

Number of consecutive failures before marking container unhealthy

Error Signatures (7)

stat /opt/code/localstack/.venv/bin/localstack: no such file or directoryerror code

OCI runtime exec failed: exec failed: unable to start container processerror code

Listening at http://:::51679log pattern

Health check exceeded timeout (5s)log pattern

-1exit code

503http status

ServiceUnavailableerror code

CLI Commands (6)

docker inspect docker.io/localstack/localstack:s3-latestdiagnostic

docker exec <container_id> /opt/code/localstack/.venv/bin/localstack status services --format=jsondiagnostic

docker inspect <container> | jq ".[].State.Health"diagnostic

.venv/bin/localstack status services --format=jsondiagnostic

curl http://localhost:4566/_localstack/healthdiagnostic

localstack status servicesdiagnostic

Technical References (15)

/opt/code/localstack/.venv/bin/localstackfile pathlocalstack status servicescomponentdocker-compose.ymlfile pathport 51679componentdocker-compose healthcheckconceptservice_healthy conditioncomponent/_localstack/healthcomponentSNS topiccomponentSQS queuecomponentmulti-region replicationconcepteventual consistencyconceptSystem status checkcomponentCloudWatch alarmcomponentTarget groupcomponentElastic IPcomponent

Related Insights (6)

Docker healthcheck fails due to missing virtualenv binary pathcritical

▸

LocalStack stops responding after showing listening message on port 51679critical

▸

LocalStack health check timeout causes false unhealthy statuswarning

▸

LocalStack health check required before test executionwarning

▸

Service or region unavailability returns 503 errors causing application failurescritical

▸

System status check failure prevents automated failover in disaster recovery setupcritical

▸