Which Podman option binds a host directory to a container path during run?

Which Podman option binds a host directory to a container path during run?

• A. -p binds host ports to container ports
• B. -v binds a host directory to a container path
• C. --name assigns a container name
• D. --network attaches the container to a network

Answer: (B)

Binding a host directory into a container happens with the volume option, using -v (or --volume). It takes the form hostPath:containerPath, for example: podman run -v /host/data:/data image. This mounts the directory from the host into the container, so files are accessible and can be shared between them (optionally read-only with :ro). The other options don’t mount directories: -p maps host ports to container ports, --name assigns a container name, and --network connects the container to a network.

Binding a host directory into a container happens with the volume option, using -v (or --volume). It takes the form hostPath:containerPath, for example: podman run -v /host/data:/data image. This mounts the directory from the host into the container, so files are accessible and can be shared between them (optionally read-only with :ro). The other options don’t mount directories: -p maps host ports to container ports, --name assigns a container name, and --network connects the container to a network.