Trying to run Docker resulted in exit code 127

Question

I am trying to run a certain application in windows that uses docker. Since the application is a shell script, I use the cygwin terminal. As am new to docker, I dont have a clear Idea as to how it works.

Using boot2docker, I have a docker terminal open in windows 7 and a cygwin terminal to run the script.

But when I run the script, say

   ./xyz init

I get the following error

    trying to run docker resulted in exit code 127

Can you please tell me what are the basic first aid I should go through to resolve this?

The application is obtained from vision.ai, called vmx. The information about the application is here.

https://docs.vision.ai/

Your help is much appreciated.

Check and confirm your volume is mapped correctly – Rasheed Oct 03 '18 at 16:18 — Rasheed, Oct 03 '18 at 16:18

Al-Mothafar · Accepted Answer · 2019-04-20T05:31:40.170

21

I got almost the same issue, the problem was simply in windows ending in that file, it was using CRLF instead of LF, change it to LF and it might work (using Notepad++, IntelliJ or Visual Code), referring to these answers:

env: bash\r: No such file or directory

How do I set all files in a subdirectory to use a specific eol using gitattributes?

So my .gitattributes file now is like this:

* text=auto
/docker/* text eol=lf
/ci/* text eol=lf
/sbt text eol=lf
/docker-*.sh text eol=lf
/sbt-dist/bin/*.bash text eol=lf
/sbt-dist/bin/sbt text eol=lf

These attributes because I have play framework project deployed in docker.

edited Apr 20 '19 at 05:31

answered Jan 09 '18 at 09:42

Al-Mothafar

7,266
6
68
96

1

I was having this same issue and solved with this answer – Carlos B. Flores Nov 10 '20 at 18:19
1

+1 Finally, after a long search I got the answer. – golchha21 Dec 23 '20 at 15:46
In the following page is how to do it in notepad++: http://sql313.com/index.php/43-main-blogs/maincat-dba/62-using-notepad-to-change-end-of-line-characters – Rendón Aug 18 '21 at 22:37

score 1 · Answer 2 · edited May 23 '17 at 12:04

1

I think the 127 means docker was not found on the path. Similar question. On windows docker will only work inside the boot2docker vm so if you are running the script in cygwin it would not work. You must ssh into the boot2docker vm and run your commands there.

edited May 23 '17 at 12:04

Community

1
1

answered Jan 07 '15 at 14:27

Usman Ismail

17,055
14
78
161

in my case i was trying to encapsulate the entire docker run command and arguments as a string. that was incorrect and did not work; I settled on using the argument terminator ` -- ` like so: `docker run ubuntu:trusty -- /usr/bin/command -a1 -b 2 argument3 argument4` – ThorSummoner Jan 04 '16 at 22:47

score 1 · Answer 3 · answered Aug 02 '17 at 07:39

1

Make sure your file has the correct line ending.

For example, open your file using Vim and run: :set fileformat=unix, then save the file and run Docker again.

answered Aug 02 '17 at 07:39

0leg

11,884
13
63
91

score 1 · Answer 4 · answered May 16 '20 at 06:12

1

I faced the same error while building in AWS CodeBuild. The issue was the sudo in the commands

In the buildspec.yml file, I had to change:

sudo docker build -t xxxx:xxxx

to

docker build -t xxxx:xxxx

answered May 16 '20 at 06:12

Suresh

435
4
11

score 0 · Answer 5 · answered Jul 18 '17 at 21:08

0

I would say Docker is not in your PATH. Add C:\Program Files\Docker\Docker\Resources\bin or appropriate

answered Jul 18 '17 at 21:08

zhrist

868
7
21

score 0 · Answer 6 · answered Apr 05 '22 at 16:41

0

here are some resources for bulk/recursive line ending conversion that can sometimes be the cause of this issue: https://gist.github.com/search?q=dos2unix

answered Apr 05 '22 at 16:41

Peter Kionga-Kamau

5,671
2
12
10

Trying to run Docker resulted in exit code 127

6 Answers6