docker-management

Check the container logs with `docker logs NAME` to see the crash output, then relaunch interactively using `docker run -it --entrypoint /bin/sh IMAGE` to inspect the environment. The main process finishing or crashing is the usual cause.

Start with `docker system df` to see what consumes space, then run targeted cleanup: `docker container prune` for stopped containers, `docker image prune` for dangling images, and `docker volume prune` for unused volumes. Avoid `docker system prune -a --volumes` unless you confirm data loss is acceptable.

Yes, Compose supports healthcheck blocks with test commands, intervals, and retries. Use `depends_on` with `condition: service_healthy` so dependent services like an API wait until a database passes its healthcheck before starting.

The application is likely binding to 127.0.0.1 inside the container, which is unreachable from the host. Configure the app to bind to 0.0.0.0 and verify the port mapping with `-p hostPort:containerPort` or `docker port NAME`.

Use multi-stage builds to separate build tools from the runtime, pick slim or alpine base images like `python:3.12-slim`, combine RUN commands to reduce layers, and add a `.dockerignore` file to exclude `node_modules` and `.git`.