The command '/bin/sh -c returned a non-zero code: 127

Exit code 127 from shell commands means "command not found". So, in your case it seems the "wget" within quotes is not being found when Docker runs it.

In some cases, the command to install wget (or whatever command-line tool is missing) must first be run in the Dockerfile because some base Docker images will not have wget. You would add a line before the failing command that looks something like this:

RUN yum install -y wget 

Do not forget you can add all lib and package you need on the same line

RUN cd /tmp \ && apt-get update \ && apt-get install -y curl apt-utils wget unzip\ && rm -rf /var/lib/apt/lists/*

Note that the error message says that wget, is not found - note the trailing comma. You’ve mixed up the “shell form” and “exec form” of the RUN command.

The “exec form” of the RUN command uses a comma-separated list of double-quoted strings wrapped in square brackets. This is identical to the syntax for JSON arrays. This form looks like this:

RUN ["wget", "http://www.us.apache.org/dist/tomcat/tomcat-6/v6.0.44/bin/apache-tomcat-6.0.44.tar.gz"] 

In exec form, the array is used to directly execute the target program with the given arguments.

The shell form, on the other hand, consists simply of the command as if it were typed in at a shell prompt, and is distinguished from the exec form by the lack of square brackets. In shell form, the entire remainder of the line is passed to the shell as /bin/sh -c <command> (note that the command is passed as a single argument, even if it contains spaces). This therefore executes the remainder of the line as a shell command, allowing you to freely use shell variables, expansions, redirections, etc.

In your case, you’ve specified your RUN command as follows:

RUN "wget", "http://www.us.apache.org/dist/tomcat/tomcat-6/v6.0.44/bin/apache-tomcat-6.0.44.tar.gz" 

Because the command doesn’t start with a square bracket, this will be interpreted as a shell form command and executed through the shell. The shell will parse and discard the double quotes, resulting in the command

wget, http://www.us.apache.org/dist/tomcat/tomcat-6/v6.0.44/bin/apache-tomcat-6.0.44.tar.gz 

The trailing comma results in the command not being found.

To fix, either use standard exec form by adding square brackets, as above, or use standard shell form:

RUN wget 'http://www.us.apache.org/dist/tomcat/tomcat-6/v6.0.44/bin/apache-tomcat-6.0.44.tar.gz' 

(Note single quotes, which are generally good practice when passing arbitrary URLs through the shell).

Even though, error code was same, but my case was different. So, sharing my insight if someone face similar problem someday.

Exit code 127 means "command not found".

At my case I was using apt-get commands with alpine image, which should be apk add instead.

Sample Code:

# Install necessary extensions at alpine-distribution RUN apk add --no-cache --update \ curl \ openssl \ *other-dependencies*