Force a disposable container to stop.
Docker / Compose: kill sends SIGKILL by default without a graceful shutdown interval.
set -euo pipefail
docker run -d --name kill-example ubuntu:20.04 sleep 300 >/dev/null
docker kill kill-example >/dev/null
docker wait kill-example >/dev/null
docker inspect --format '{{.State.ExitCode}}' kill-example
docker rm kill-example >/dev/nullExpected output EXAMPLE
137
Details
Requires Docker Engine and Docker Compose (the docker compose command). Run in a disposable development environment with ubuntu:20.04 available locally. See the input setup for any starting containers or files. kill sends SIGKILL by default without a graceful shutdown interval.
Prefer docker stop for applications that need to flush data. This example targets only its own disposable sleep process.
Tested on Alpine Linux v3.24 · · Client 29.9.0; Engine 29.9.0 · Compose 5.6.0; ubuntu:20.04
Test inputs, results and environment
The exact published code ran in a dedicated Linux test container with prepared inputs. Dedicated nested Docker daemon in a privileged test helper with no host Docker socket. No application data or host directories are mounted into the example containers. The outer helper has networking disabled; the base image is preloaded. Dockerfile examples are built and run; Compose examples start real containers. Fixtures and output records are isolated from the application database. Testing covers this example and its stated checks, not every input, operating system, or runtime version. The Linux container shares its host's kernel; this is not a native Windows test.
- Architecture / host kernel
- x86_64 / 6.18.54.1-microsoft-standard-WSL2
- Snippet identity / locale
- root inside disposable Docker-in-Docker helper / C.UTF-8
- Interpreter invocation
bash -euo pipefail -c <published code>- Container image ID
sha256:aa45302a315fcbba307d6749ccbbac83af2e6f9447d6d714fce5b7b1c92b1081- Code SHA-256
894496f30fa8be6819c0c402e99346dbdef58beba0d283c66ed0bcfeb337278f- Dependencies
- Compose 5.6.0; ubuntu:20.04
Test input setup
These are the prepared inputs used by the test harness. See Details above for the prerequisites and how to run this example.
# No input files required.
Observed standard output
137
Exit code: 0. Standard error: empty. Validation: Exact stdout comparison. System-dependent values above are one recorded run.
Additional assertions that passed
Checks recorded by the test harness. Where Python assertions are shown, browser cases use Playwright and simulator cases may inspect pin transitions: result.stdout is captured output, work is the temporary directory, and Path is pathlib.Path. The harness also imports json and csv.
All commands returned zero; exact output matched.