bash: ./deploy.sh: /bin/bash^M: bad interpreter: No such file or directory` · Issue #1 · openvlc/OpenVLC · GitHub
![Resolving "/bin/bash^M: bad interpreter" with a Shellscript written on Windows in VS Code run on Linux - ztirom Resolving "/bin/bash^M: bad interpreter" with a Shellscript written on Windows in VS Code run on Linux - ztirom](https://i0.wp.com/ztirom.at/wp-content/uploads/2016/01/bin_bash_M_bad_interpreter_vscode_win_2.png?resize=630%2C115&ssl=1)
Resolving "/bin/bash^M: bad interpreter" with a Shellscript written on Windows in VS Code run on Linux - ztirom
bin/bash^M: bad interpreter: No such file or directory · Issue #5 · mattddowney/compose-postgrest · GitHub
![Build a Build Script: ./script.sh : /bin/bash : bad interpreter : No such file or directory - Command Line - Codecademy Forums Build a Build Script: ./script.sh : /bin/bash : bad interpreter : No such file or directory - Command Line - Codecademy Forums](https://global.discourse-cdn.com/codecademy/original/5X/f/9/b/6/f9b68b002ef1d77388711b4dd4f709d6f2831da0.png)
Build a Build Script: ./script.sh : /bin/bash : bad interpreter : No such file or directory - Command Line - Codecademy Forums
![Resolving "/bin/bash^M: bad interpreter" with a Shellscript written on Windows in VS Code run on Linux - ztirom Resolving "/bin/bash^M: bad interpreter" with a Shellscript written on Windows in VS Code run on Linux - ztirom](https://i0.wp.com/ztirom.at/wp-content/uploads/2016/01/bin_bash_M_bad_interpreter_vscode_win_1.png?fit=352%2C118&ssl=1)
Resolving "/bin/bash^M: bad interpreter" with a Shellscript written on Windows in VS Code run on Linux - ztirom
![Build a Build Script: ./script.sh : /bin/bash : bad interpreter : No such file or directory - Command Line - Codecademy Forums Build a Build Script: ./script.sh : /bin/bash : bad interpreter : No such file or directory - Command Line - Codecademy Forums](https://global.discourse-cdn.com/codecademy/original/5X/3/5/2/6/3526e0226b2afa378a957fb5ed04734c37a4a345.png)