Docker command fails during build, but succeeds while executed within running container

Question

the command :

docker build -t nginx-ubuntu .

whith the Dockerfile below :

FROM ubuntu:12.10
RUN apt-get update
RUN apt-get -y install libpcre3 libssl-dev
RUN apt-get -y install libpcre3-dev
RUN apt-get -y install wget zip gcc
RUN wget http://nginx.org/download/nginx-1.4.1.tar.gz
RUN gunzip nginx-1.4.1.tar.gz
RUN tar -xf nginx-1.4.1.tar
RUN wget --no-check-certificate https://github.com/max-l/nginx_accept_language_module/archive/master.zip
RUN unzip master
RUN cd nginx-1.4.1
RUN ./configure --add-module=../nginx_accept_language_module-master --with-http_ssl_module --with-pcre=/lib/x86_64-linux-gnu --with-openssl=/usr/lib/x86_64-linux-gnu

Fails at the last line (./configure ...)

If I remove the last line and run a bash in the container, and execute the last line manually, it works.

I would expect that whatever command runs successfully within a container should work when the command is appended in the Dockerfile (prefixed by RUN)

am I missing something ?

creack · Accepted Answer · 2013-07-26 22:24:16Z

53

The pwd is not persistent across RUN commands. You need to cd and configure within the same RUN.

This Dockerfile works fine:

FROM ubuntu:12.10
RUN apt-get update
RUN apt-get -y install libpcre3 libssl-dev
RUN apt-get -y install libpcre3-dev
RUN apt-get -y install wget zip gcc
RUN wget http://nginx.org/download/nginx-1.4.1.tar.gz
RUN gunzip nginx-1.4.1.tar.gz
RUN tar -xf nginx-1.4.1.tar
RUN wget --no-check-certificate https://github.com/max-l/nginx_accept_language_module/archive/master.zip
RUN unzip master
RUN cd nginx-1.4.1 && ./configure --add-module=../nginx_accept_language_module-master --with-http_ssl_module --with-pcre=/lib/x86_64-linux-gnu --with-openssl=/usr/lib/x86_64-linux-gnu

answered Jul 26, 2013 at 22:24

creack

123k12 gold badges101 silver badges73 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

e18r Over a year ago

Use WORKDIR instead of cd. See @alanfalloon's answer.

alanfalloon · Accepted Answer · 2014-04-04 18:43:38Z

31

As an alternative to @creak's answer, you can change the default working directory in a Dockerfile with the WORKDIR command:

FROM ubuntu:12.10
# Run update & install together so that the docker cache doesn't
# contain an out-of-date APT cache (leading to 404's when installing
# packages)
RUN apt-get update && DEBIAN_FRONTEND=noninteractive apt-get -y install libpcre3 libssl-dev libpcre3-dev wget zip gcc
ADD http://nginx.org/download/nginx-1.4.1.tar.gz nginx-1.4.1.tar.gz
RUN tar -zxf nginx-1.4.1.tar.gz
RUN wget --no-check-certificate https://github.com/max-l/nginx_accept_language_module/archive/master.zip
RUN unzip master
WORKDIR nginx-1.4.1
RUN ./configure --add-module=../nginx_accept_language_module-master --with-http_ssl_module --with-pcre=/lib/x86_64-linux-gnu --with-openssl=/usr/lib/x86_64-linux-gnu

This also affects the default directory when you use docker run (overridden by the -w switch).

answered Apr 4, 2014 at 18:43

alanfalloon

4434 silver badges6 bronze badges

2 Comments

ThatsNinja Over a year ago

+1 WORKDIR is the correct way to set the working directory during a container build, as it applies to all the 'RUN, CMD, ENTRYPOINT, COPY, and ADD instructions that follow it'.

Pumphouse Over a year ago

this does not work for me. The file isn't available when I change WORKDIR

Pumphouse · Accepted Answer · 2016-06-08 03:35:06Z

2

When I called wget or tar with RUN I needed to specify a path, it looks like ADD is the correct approach if you want to use WORKDIR as it's path instead. So either of the below resolved my issue.

RUN

RUN wget http://nginx.org/download/nginx-1.4.1.tar.gz -P ~/directory
RUN tar -zxf ~/directory/nginx-1.4.1.tar.gz -C ~/directory

or

ADD

WORKDIR ~/directory
ADD http://nginx.org/download/nginx-1.4.1.tar.gz nginx-1.4.1.tar.gz
RUN tar -zxf nginx-1.4.1.tar.gz

The second approach prevented me from needing to install wget in the container.

edited Jun 8, 2016 at 3:35

answered Jun 8, 2016 at 3:10

Pumphouse

2,05317 silver badges26 bronze badges

Comments

Chammaar · Accepted Answer · 2022-09-16 19:01:09Z

1

Another way of doing this using the \ operator to start a new line and proceed with an additional command

Example

RUN cd /Desktop \ 
    cd Work \   
    pwd

edited Sep 16, 2022 at 19:01

answered Sep 16, 2022 at 19:00

Chammaar

611 silver badge4 bronze badges

Comments

MattC · Accepted Answer · 2024-08-20 16:57:36Z

0

One solution is to run multiple commands, as many as you want, in a single RUN with &&:

RUN cd nginx-1.4.1 && ./configure --add-module=../nginx_accept_language_module-master --with-http_ssl_module --with-pcre=/lib/x86_64-linux-gnu --with-openssl=/usr/lib/x86_64-linux-gnu

or include a backslash, && \ if wanting to continue on the next line:

RUN cd nginx-1.4.1 && \
    ./configure --add-module=../nginx_accept_language_module-master --with-http_ssl_module --with-pcre=/lib/x86_64-linux-gnu --with-openssl=/usr/lib/x86_64-linux-gnu

answered Aug 20, 2024 at 16:57

MattC

6,4641 gold badge54 silver badges43 bronze badges

Collectives™ on Stack Overflow

Docker command fails during build, but succeeds while executed within running container

5 Answers 5

1 Comment

2 Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

1 Comment

2 Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related