Unable to prepare context: path ".\r" not found

Question

I have created build_docker.sh file in windows machine which has below contents.

#!/usr/bin/env bash
#This script build docker image
docker build -t hello-world .

Where I try to run above file using command sudo sh build_docker.sh
It fails with an error, Unable to prepare context: path ".\r" not found
I am using 4.2.46(2)-release Bash version

What I am missing here?

`\r` is a common escape for a literal carriage return. Check for DOS newlines. — Charles Duffy, Feb 07 '19 at 10:35
BTW, this is the very first thing in "before asking about problematic code" in https://stackoverflow.com/tags/bash/info — Charles Duffy, Feb 07 '19 at 10:36
I tried to edit this file to remove `\r` still facing same issue — Mayur, Feb 07 '19 at 10:36
Possible duplicate of [How to convert DOS/Windows newline (CRLF) to Unix newline (LF) in a Bash script?](https://stackoverflow.com/q/2613800/608639) — jww, Feb 07 '19 at 10:36
Tried to edit it *how*? If you opened it in vim, run `:set fileformat=unix` before saving. An editor that things you *want* your file to be saved in DOS format instead of UNIX format will just create CRLFs again when it saves your changes. — Charles Duffy, Feb 07 '19 at 10:37
BTW, if your script has a `#!/usr/bin/env bash` shebang, you should use `sudo bash`, not `sudo sh`, to run it (or even better, fix its permissions and just run `sudo ./yourscript`). `bash` and `sh` are two different shells, and much code that runs in bash doesn't work in sh. — Charles Duffy, Feb 07 '19 at 10:39
Your `sh` is not `bash`, so the bash version you're using interactively doesn't make any difference whatsoever. Anyhow, that's not part of the problem but is a general aside re: practice issues that'll bite you later. — Charles Duffy, Feb 07 '19 at 10:40
That won't fix the problem, which is still caused by CRLFs. But if you changed your script in the future to use bash-only features, it would fail when you start it with `sh`. — Charles Duffy, Feb 07 '19 at 10:41
It is recommended use `.sh` for files in the POSIX sh language and `.bash` for bash shell scripts. — Jackdaw, Oct 18 '20 at 10:04
I think this link https://stackoverflow.com/a/40821931/1375110 gives correct solution if using git — Satish, Mar 03 '23 at 04:38

score 3 · Answer 1 · answered Apr 02 '21 at 19:57

3

There is an utility to convert file to unix EOL, it helped me.

dos2unix build_docker.sh

answered Apr 02 '21 at 19:57

Vladimir Buskin

614
4
8

Thanks! this worked for me. had to install this tool using command, sudo apt install dos2unix – Prabuddha Kulatunga May 20 '21 at 14:39

score 2 · Accepted Answer · edited Feb 08 '19 at 10:02

2

… using :set fileformat=unix and sudo bash build_docker.sh solved my problem – Mayur

edited Feb 08 '19 at 10:02

Mayur

2,583
16
28

answered Feb 08 '19 at 09:33

Armali

18,255
14
57
171

score 2 · Answer 3 · answered Oct 18 '20 at 07:27

2

changing file name from filename.sh to .bash solved my issue.

answered Oct 18 '20 at 07:27

ticktack

21
2

Good to know that! – Mayur Oct 19 '20 at 08:10

score 1 · Answer 4 · answered Jun 18 '20 at 13:01

1

This will also work.

1. Open all files using vim *
2. Press "qq" to start recording
3. :set ff=unix
4. :wn
5. Press again "q" to stop recording
6. :wq!

answered Jun 18 '20 at 13:01

techmagister

1,188
8
14

Thanks for commenting! – Mayur Jun 18 '20 at 14:33

Unable to prepare context: path ".\r" not found

4 Answers4