{"id":208,"date":"2020-04-03T10:51:01","date_gmt":"2020-04-03T10:51:01","guid":{"rendered":"http:\/\/shresthabrijan.com.np\/?p=208"},"modified":"2020-04-03T11:22:36","modified_gmt":"2020-04-03T11:22:36","slug":"lets-talk-about-dockerfile","status":"publish","type":"post","link":"https:\/\/shresthabrijan.com.np\/?p=208","title":{"rendered":"Let’s talk about Dockerfile"},"content":{"rendered":"\n

Docker provides a way to build an image by reading a set of instructions. Dockerfile is the file containing such instructions which is read by docker build<\/strong> <\/em>command to generate an image.<\/p>\n\n\n\n

$docker build <context>\n\nThe command, docker build, is passed with either of two context, PATH or URL. \nPath is the location in local filesystem whereas URL is git repo location. \nThis makes the docker build pass the content of whole context to docker daemon recursively.\n\nUsage:\n$docker build -f \/path\/to\/Dockerfile \/project\n$docker build -t newproject .\n\nNote:\nEach line of instruction inside Dockerfile is executed independently and if required separate image is generated for each command simultaneously until the final image is created\nDocker excludes files and dirs listed in .dockerignore file while sending the context.<\/pre>\n\n\n\n
Inside the Dockerfile<\/h5>\n\n\n\n
Instructions inside dockerfile are usually entered in following format:<\/p>\n\n\n\n
# Comment\nINSTRUCTION arguments<\/pre>\n\n\n\n
 Common Instructions <\/strong><\/h6>\n\n\n\n
FROM<\/strong>

Every dockerfile must begin with a FROM instruction which defines the parent image with which the subsequent image is to be built. However, it may be preceded by  parser directive, comment and\/or global scope ARGs

Usage:
FROM [–platform=<platform>] <image>[:<tag>] [AS <name>]

–platform flag can be used to specify platform of an image
Specifying image name helps inf future reference of image built in the stage
E.g. FROM –platform=linux\/amd64 Ubuntu:18.04 AS newimage<\/p>\n\n\n\n
RUN<\/strong>

RUN instruction is used to execute command and commit the results on top of current image as a result it can be used in next set of instructions. 

Usage:
RUN <command> 
This will execute the command using shell which which by default is \/bin\/sh -c on Linux or cmd \/S \/C on Windows
e.g. RUN echo Hello!

RUN [“executable”, “param1”, “param2”]
To use other than shell to run commands, this format is used
e.g. RUN [“D:\\script.bat”, “arg”]<\/p>\n\n\n\n
CMD<\/strong>

This instruction is use to define defaults for an executing container as a result there can be only one of it. Multiple declaration of CMD in a dockerfile will automatically use the last CMD as default. 

Usage:
CMD [“executable”,”param1″,”param2″]
This is the exec form for running CMD. 
e.g. CMD [“\/bin\/ls”, “-l”]

CMD [“param1″,”param2”]
This is used to pass arguments to ENTRYPOINT. 

CMD command param1 param2
This form is used to execute command in a shell.
e.g. CMD echo “Hello World!”<\/p>\n\n\n\n
ENTRYPOINT<\/strong>

Defining ENTRYPOINT allows to configure a container to run a command on start of container similar to CMD but the major difference is arguments passed while running container is appended to ENTRYPOINT command while the CMD command is completely replaced by them.
i.e. For $docker run <image> arg1<\/em><\/span><\/code> , arg1 will be appended on ENTRYPOINT whereas it will replace CMD.

Usage:
ENTRYPOINT [“executable”, “param1”, “param2”]
This is termed exec form and is parsed as JSON array.  It can use CMD to set extra parameters which can be changed by user while running a container.
e.g.
ENTRYPOINT [“\/bin\/ls”, “-l”]
CMD [“-a”]

ENTRYPOINT command param1 param2
This is termed as shell form and executes the command using shell. To ensure proper exit, command should be preceded by exec.
e.g. ENTRYPOINT exec ls -l <\/p>\n\n\n\n
EXPOSE<\/strong>

The EXPOSE instruction defines a port that the container listens on. By default, it assumes tcp port unless defined specifically.
e.g. EXPOSE 80\/tcp or EXPOSE 1234\/udp

Note:
The ports defined by EXPOSE are not published by default. User has to manually define ports using -p flag during docker run or explicitly publish all exposed ports using -P. So, this is more like a documentation for maintainers.<\/p>\n\n\n\n
ENV<\/strong>

As the name suggests, this instruction sets environment variable which remains persistent during container creation.

Usage:
ENV <key> <value>
ENV <key>=<value>

e.g. ENV name Fname Lname
        ENV name=Fname\\ Lname address=”Home Town”<\/p>\n\n\n\n
   ADD<\/strong>

This instruction copies files and dirs from given source in context to the image. The source can be local filesystem or remote url as well.

Usage:
ADD <src> <dest>
e.g. ADD testdir \/project
        ADD https:\/\/example.com\/repo \/project

For linux containers, ADD supports [–chown=<user>:<group>] parameter for hadnling user and group administration<\/p>\n\n\n\n
COPY<\/strong>

Copy does the same job as ADD but does not supports URL copying.<\/p>\n\n\n\n
VOLUME<\/strong>

VOLUME instruction creates mount point in the image with the name defined in parameter which can be referred by other containers. 

Usage:
VOLUME [“\/data”]
e.g. VOLUME \/newvol<\/p>\n\n\n\n
WORKDIR<\/strong>

This instruction sets working directory which is used by other instructions. A container created using the image will start in the location defined in WORKDIR. 

Usage:
WORKDIR \/path\/to\/workdir<\/p>\n\n\n\n
USER<\/strong>

USER instruction helps to define user and optionally group which will be used to run commands during image creation.

Usage:
USER <user>[:<group>] or
            <uid>[:<gid>]
e.g. USER foo<\/p>\n\n\n\n
For more details on the Dockerfile, visit the docker documentation<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Docker provides a way to build an image by reading a set of instructions. Dockerfile is the file containing such instructions which is read by docker build command to generate an image. $docker build <context> The command, docker build, is passed with either of two context, PATH or URL. Path is the location in local […]<\/p>\n
Read More<\/a><\/div>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-208","post","type-post","status-publish","format-standard","hentry","category-system-administration"],"_links":{"self":[{"href":"https:\/\/shresthabrijan.com.np\/index.php?rest_route=\/wp\/v2\/posts\/208","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/shresthabrijan.com.np\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/shresthabrijan.com.np\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/shresthabrijan.com.np\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/shresthabrijan.com.np\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=208"}],"version-history":[{"count":14,"href":"https:\/\/shresthabrijan.com.np\/index.php?rest_route=\/wp\/v2\/posts\/208\/revisions"}],"predecessor-version":[{"id":222,"href":"https:\/\/shresthabrijan.com.np\/index.php?rest_route=\/wp\/v2\/posts\/208\/revisions\/222"}],"wp:attachment":[{"href":"https:\/\/shresthabrijan.com.np\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=208"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/shresthabrijan.com.np\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=208"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/shresthabrijan.com.np\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=208"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}