問題文
An image declares a port in its build file, but a client on the host still cannot reach the service. What does that declaration actually do, and what is missing?
選択肢
- The declaration in the build file is only metadata for whoever reads the image and does not open any mapping on the host, so the operator must also map a host port to the container port when the container is stopped, which the engine records as a published identity of that container.
- The declaration in the build file is only metadata for whoever reads the image and does not open any mapping on the host, so the operator must also map a host port to the container port when the container is created, which the engine records as a published binding of that container.
- The declaration in the build file is only encryption for whoever reads the image and does not open any account on the host, so the operator must also map a host port to the container port when the container is created, which the engine records as a published binding of that container.
- The declaration in the build file is only encryption for whoever reads the image and does not open any account on the host, so the operator must also map a host port to the container port when the container is stopped, which the engine records as a published identity of that container.