Which command produces a Dockerfile from an S2I build?

Which command produces a Dockerfile from an S2I build?

• A. s2i build <sourcecode> <image> <name> --as-dockerfile <destination>/Dockerfile
• B. s2i build --as-dockerfile <destination>/Dockerfile <sourcecode> <image> <name>
• C. s2i create-dockerfile <sourcecode> <image> <name> --as-dockerfile
• D. s2i build <image> <name> --dockerfile <destination>/Dockerfile

Answer: (A)

S2I can generate a Dockerfile that mirrors how the image would be built. To create that Dockerfile, you run the build command with the source, the builder image, and a name, then specify the output path with the --as-dockerfile option. The correct form is s2i build <sourcecode> <image> <name> --as-dockerfile <destination>/Dockerfile. This writes the Dockerfile to the given location so you can inspect or modify it. The other options don’t fit: there is no create-dockerfile subcommand, and the flag to generate a Dockerfile is --as-dockerfile (not --dockerfile), and the typical usage places the flag after the required arguments.

S2I can generate a Dockerfile that mirrors how the image would be built. To create that Dockerfile, you run the build command with the source, the builder image, and a name, then specify the output path with the --as-dockerfile option. The correct form is s2i build --as-dockerfile /Dockerfile. This writes the Dockerfile to the given location so you can inspect or modify it. The other options don’t fit: there is no create-dockerfile subcommand, and the flag to generate a Dockerfile is --as-dockerfile (not --dockerfile), and the typical usage places the flag after the required arguments.