meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
linux:docker:dockerfile [2017/02/10 12:34] – niziaklinux:docker:dockerfile [2021/05/16 18:02] (current) – niziak
Line 1: Line 1:
 +====== Dockerfile ======
 +
 +====== Build process ======
 +
 +Docker process ''Dockerfile'' stepping through the instructions.
 +[[https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/#/build-cache]]
 +
 +==== FROM ====
 +
 +==== ENTRYPOINT ====
 +
 +==== RUN ====
 +
 ==== ADD ==== ==== ADD ====
 [[https://docs.docker.com/engine/reference/builder/#/add]] [[https://docs.docker.com/engine/reference/builder/#/add]]
Line 28: Line 41:
 > >
 >Although ADD and COPY are functionally similar, generally speaking, COPY is preferred. That’s because it’s more transparent than ADD. COPY only supports the basic copying of local files into the >container, while ADD has some features (like local-only tar extraction and remote URL support) that are not immediately obvious. Consequently, the best use for ADD is local tar file auto-extraction >into the image, as in ADD rootfs.tar.xz /. >Although ADD and COPY are functionally similar, generally speaking, COPY is preferred. That’s because it’s more transparent than ADD. COPY only supports the basic copying of local files into the >container, while ADD has some features (like local-only tar extraction and remote URL support) that are not immediately obvious. Consequently, the best use for ADD is local tar file auto-extraction >into the image, as in ADD rootfs.tar.xz /.
 +
 +
 +==== EXPOSE ====
 +==== VOLUME ====