Start a Linux container image with an ordinary Linux container runtime.
Which host relationship is an important constraint?
Because containers share the host kernel, the image and workload need compatible CPU architecture and kernel features. The userland distribution can differ.
Detailed explanation
Incorrect. Architecture and kernel features still constrain container execution.
Incorrect. Architecture and kernel features still constrain container execution.
Incorrect. A container userland does not always need the same distribution as the host.
Incorrect. A container userland does not always need the same distribution as the host.
Correct. The shared kernel requires compatible architecture and features.
Correct. The shared kernel requires compatible architecture and features.
Incorrect. Containers do not automatically overwrite host configuration files.
Incorrect. Containers do not automatically overwrite host configuration files.
Try it yourself
An example you can run in a temporary verification environment.
uname -m; uname -rExpected result
host側から見えるarchitectureとkernel releaseKey points
- Architecture
- Kernel compatibility
- User space
Notes
- Environment: Linux container host
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Read the scope first
Check whether the command acts on the current shell, a new process, an existing process, or a file.
Verify the observable result
Use the supplied command and compare the output with the expected result.