This is actually the structure associated with Dockerfile :
The instruction isn’t case-sensitive. Nonetheless, meeting is from arguments more easily for them to be UPPERCASE to distinguish them.
Docker operates directions in a Dockerfile if you wish. A Dockerfile must start with A off instruction. This might be after parser directives, reviews, and globally scoped ARGs. The FROM instruction specifies the Parent Image from where you’re building. FROM may just be preceded by more than one ARG guidelines, which declare arguments which are found in OFF lines within the Dockerfile .
Docker treats lines that start with # as a remark, unless the line is a legitimate parser directive. A # marker anywhere else in line is addressed as a disagreement. This permits statements like:
Remark lines are eliminated prior to the Dockerfile guidelines are performed, meaning that the remark into the following example is perhaps maybe perhaps not managed because of the shell performing the echo demand, and both examples here are comparable:
Line continuation characters aren’t supported in feedback.
For backward compatibility, leading whitespace before responses ( # ) and directions (such as for example RUN ) are ignored, but discouraged. Leading whitespace just isn’t preserved in such cases, plus the examples that are following consequently comparable:
Note however, that whitespace in instruction arguments, for instance the commands after RUN , are preserved, so that the example that is following ` hello world` with leading whitespace as specified: