Run an ordinary Linux container on a Linux host.
Which statement about the container kernel is correct?
A normal Linux container does not boot a separate kernel; its processes use the host Linux kernel with isolation mechanisms.
Detailed explanation
Incorrect. Containers do not each reserve a physical CPU.
Incorrect. A standard container does not start another hypervisor.
Incorrect. The kernel inside an image is not normally booted by the container runtime.
Correct. Container processes share the host Linux kernel.
Try it yourself
An example you can run in a temporary verification environment.
readlink /proc/self/ns/pidExpected result
現在processが属するPID namespace識別子Key points
- Shared kernel
- Namespaces
- OS-level virtualization
Notes
- Environment: Linux namespace対応kernel
- Use a disposable VM or container when validating lifecycle commands.
- Exact command output can vary slightly by distribution and runtime version.
Foundation review
Identify the layer
Resource limits and process namespaces add isolation, but they do not turn a normal container image into a bootable VM.
Check the side effect
Inspect namespace identifiers and the host kernel version without assuming that a container contains a separate kernel.