Which command builds an S2I builder image with Podman using a directory and a specific tag NAME:TAG?

Which command builds an S2I builder image with Podman using a directory and a specific tag NAME:TAG?

• A. sudo podman build -t <name> .
• B. sudo podman build -t NAME:TAG DIR
• C. podman build -t <name> DIR
• D. sudo docker build -t <name> DIR

Answer: (B)

The key idea is how Podman builds and tags an image in one step. The -t flag assigns a tag to the image in the form NAME:TAG, where NAME is the repository and TAG is the version or label you want to give it. The final argument specifies the build context directory; Podman looks in that directory for a Dockerfile (or similar build instructions) and uses its contents to build the image. The best command uses Podman, tags the image as NAME:TAG, and sets the build context to the specified directory DIR. It’s common to prepend sudo if your environment requires root privileges, but the essential parts are Podman, -t NAME:TAG, and DIR. Why the other forms don’t fit: one omits the tag and uses a generic name, another uses a current directory without providing the correct tag, and another switches to Docker instead of Podman.

The key idea is how Podman builds and tags an image in one step. The -t flag assigns a tag to the image in the form NAME:TAG, where NAME is the repository and TAG is the version or label you want to give it. The final argument specifies the build context directory; Podman looks in that directory for a Dockerfile (or similar build instructions) and uses its contents to build the image.

The best command uses Podman, tags the image as NAME:TAG, and sets the build context to the specified directory DIR. It’s common to prepend sudo if your environment requires root privileges, but the essential parts are Podman, -t NAME:TAG, and DIR.

Why the other forms don’t fit: one omits the tag and uses a generic name, another uses a current directory without providing the correct tag, and another switches to Docker instead of Podman.