In terms of the way Docker works, is there any difference between RUN cd /
and WORKDIR /
inside a Dockerfile?
RUN cd /
does absolutely nothing. WORKDIR /
changes the working directory for future commands.
Each RUN
command runs in a new shell and a new environment (and technically a new container, though you won't usually notice this). The ENV
and WORKDIR
directives before it affect how it starts up. If you have a RUN
step that just changes directories, that will get lost when the shell exits, and the next step will start in the most recent WORKDIR
of the image.
FROM busybox
WORKDIR /tmp
RUN pwd # /tmp
RUN cd / # no effect, resets after end of RUN line
RUN pwd # still /tmp
WORKDIR /
RUN pwd # /
RUN cd /tmp && pwd # /tmp
RUN pwd # /
(For the same reason, RUN export
doesn't do anything that outlives the current Dockerfile instructions, and RUN.
or the non-standard RUN source
won't cause environment variables to be set.)
Doesn't it happen if you just try
RUN cd /
?
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.