問題文
A program inside a container expects a scheduler to run a periodic task and expects an init system to reap orphaned children. Which of those assumptions can it keep, and what should replace them?
選択肢
- The periodic work should move to a sidecar owned by the platform rather than to a daemon inside the volume, and the reaping problem is solved by a tiny init as the first process, because the process with the lowest identifier inside a container does not behave like a full dispatcher and will not adopt an orphaned thread by itself.
- The periodic work should move to a controller owned by the platform rather than to a daemon inside the image, and the reaping problem is solved by a tiny init as the first process, because the process with the lowest identifier inside a container does not behave like a full supervisor and will not adopt an orphaned process by itself.
- The periodic work should move to a controller owned by the platform rather than to a daemon inside the image, and the reaping problem is solved by a tiny init as the first process, because the process with the lowest identifier inside a container does not behave like a full dispatcher and will not adopt an orphaned thread by itself.
- The periodic work should move to a sidecar owned by the platform rather than to a daemon inside the volume, and the reaping problem is solved by a tiny init as the first process, because the process with the lowest identifier inside a container does not behave like a full supervisor and will not adopt an orphaned process by itself.