You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I enter to the workspace container, I get this error:
$ winpty docker-compose exec workspace bash
bash: $'\r': command not found
bash: $'\r': command not found
bash: /root/aliases.sh: line 119: syntax error near unexpected token `$'{\r''
'ash: /root/aliases.sh: line 119: `function mkd() {
Have the same issue. This is somehow related to windows line endings (CRLF) in aliases.sh. After manually changing CRLF to LF in aliases.sh and rebuilding and restarting the workspace container, the issue disappeared. CRLF in *.sh files is never a good thing. Why don't we add a .gitattributes file to the repo, so we could control that all *.sh files are checked out with LF, regardless of the local settings on user side. Following configuration could the trick:
Description:
When I enter to the workspace container, I get this error:
Expected Behavior:
No error :-)
Context information:
Output of
git rev-parse HEAD
Output of
docker version
Output of
docker-compose version
System info: Mac, Windows or Linux. Include which disto/version
Steps to reproduce the issue:
docker-compose up -d nginx mysql workspace phpmyadmin
winpty docker-compose exec workspace bash
Stacktrace & Additional info:
All files are unmodified.
The text was updated successfully, but these errors were encountered: