Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

‘bash\r’ not such file, after building the container locally #4

Open
yarimiz opened this issue Dec 10, 2021 · 1 comment
Open

Comments

@yarimiz
Copy link
Contributor

yarimiz commented Dec 10, 2021

I'm facing an issue running the ibgateway container, only when building it locally.

The following log appears after running either docker-compose up or docker run (with the required environment variables and ports)

Creating network "ibgateway_default" with the default driver
Creating ibgateway_gateway_1 ... done
Attaching to ibgateway_gateway_1
gateway_1  | *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh...
gateway_1  | *** Running /etc/my_init.d/10_syslog-ng.init...
gateway_1  | Dec 10 06:27:53 c09fbb0543d4 syslog-ng[14]: syslog-ng starting up; version='3.13.2'
gateway_1  | *** Booting runit daemon...
gateway_1  | *** Runit started as PID 23
gateway_1  | /usr/bin/env: /usr/bin/env: ‘bash\r’‘bash\r’: No such file or directory
gateway_1  | : No such file or directory
gateway_1  | /usr/bin/env: ‘bash\r’: No such file or directory
gateway_1  | /usr/bin/env: ‘bash\r’: No such file or directory
gateway_1  | Dec 10 06:27:54 c09fbb0543d4 cron[30]: (CRON) INFO (pidfile fd = 3)
gateway_1  | Dec 10 06:27:54 c09fbb0543d4 cron[30]: (CRON) INFO (Running @reboot jobs)
gateway_1  | /usr/bin/env: /usr/bin/env: /usr/bin/env: ‘bash\r’‘bash\r’: No such file or directory
gateway_1  | : No such file or directory
gateway_1  | ‘bash\r’: No such file or directory
gateway_1  | /usr/bin/env: ‘bash\r’: No such file or directory

This happens only if I'm trying to run a locally built container, using docker build ., as specified in the readme.

I tried building and running the container on Windows 10 and WSL2 Ubuntu but the issue persist.

This is probably because the EOL in the run files are using \r\n for some reason, even though I've built the container using WSL2, which is supposed to not add the windows style EOL to existing files.

Update:
Building the image using MacOS solves the issue. But the windows compatibility is a bug that should be fixed.
I'll try fixing it my own and creating a PR, but not sure yet how to fix it.

@mgvazquez
Copy link
Owner

Hi @yarimiz
First at all, sorry for the delay.
I don't have a Windows environment where can test it, so I will appreciate any help you can give me with this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants