* Format of FROM instruction: In addition to the two variations shown in the man page, I understand there is also a "image@digest" form. * Minor nit -- might be useful to add that MAINTAINER can also take a general URL that represents the owner of the Dockerfile, like http://fedoraproject.org/wiki/Cloud * "There can be only one CMD in a Dockerfile." Well, no, there *can* be more than one but, as you point out in the next line, only the last one counts. I would reword that as, "There should be only one CMD in a Dockerfile." * Apparently, the LABEL instruction can also accept a space instead of an equal sign -- that's not mentioned in the man page. * Under "ENV", "RUN" is not in bold as are "ENTRYPOINT" and "CMD". * Under "ADD", I don't see any mention that it can handle tarballs. I think that's it.
Couple more observations on "man Dockerfile", even though I think that entire page could be rewritten. First, there is no mention that both COPY and ADD can take archive-type arguments (tar, gzip, bzip2); *however*, I just learned that such archive files will be automatically unpacked only if they're local -- archives copied via URL will NOT be automatically unpacked. (Side note: https://labs.ctl.io/dockerfile-add-vs-copy/ is a decent blog post basically saying don't use ADD at all, and it makes a compelling argument.) Also, it might be worth mentioning that LABEL is useful not only for adding arbitrary metadata to an image, but in the context of atomic hosts as explained here: https://github.com/projectatomic/atomic/ But that's a judgment call.
I think adding the information on ADD/COPY would be appropriate. Adding information on LABEL, might be controversial, since we use it for tooling but not in docker in general. Might be able to list some potential use cases of LABEL though.
submitted https://github.com/docker/docker/pull/16043
Seems to be a missing ] here: LABEL [<key>[ <value>]
merged https://github.com/docker/docker/pull/16043 (and fixed errant [) :)
Fixed in docker-1.9