Which statement about Init Containers is true?

Which statement about Init Containers is true?

• A. They run after the main container finishes
• B. They run before the main application container starts
• C. They run only if the Pod requests extended resources
• D. They run in a different namespace

Answer: (B)

Init containers run to completion before the main application containers in the same Pod start. They execute in order, and the Pod won’t proceed to start the app containers until every init container has successfully finished. This setup lets you perform bootstrap tasks—such as environment checks, migrations, or data preparation—before the application code runs, all sharing the same Pod namespace and volumes. If an init container fails, the Pod stays waiting and won’t launch the main containers until it succeeds. They don’t run after the main containers, they don’t depend on extended resources, and they run in the same namespace as the Pod.

Init containers run to completion before the main application containers in the same Pod start. They execute in order, and the Pod won’t proceed to start the app containers until every init container has successfully finished. This setup lets you perform bootstrap tasks—such as environment checks, migrations, or data preparation—before the application code runs, all sharing the same Pod namespace and volumes. If an init container fails, the Pod stays waiting and won’t launch the main containers until it succeeds. They don’t run after the main containers, they don’t depend on extended resources, and they run in the same namespace as the Pod.