Containers not playing on Windows

[alirazacodes]

Expected Behavior

I'm testing sBTC on Windows OS, the containers such as bitcoin, miner, electrs, stacks, sbtc, are supposed to be started when hit play button.

Actual Behavior

So when I try to hit the play button in front of those containers, they show status like 'Exited(1)' or 'Exited(127)'.

Steps to Reproduce

1. I'm using Windows OS, and docker installed on it, using VSCode as IDE, and when I try to run the commands on VSCode, it opens the git bash and run there, if I directly run them on the git bash then it runs there.
2. I followed the commands stated in the code such as ./build.sh and ./up.sh
3. Attaching logs on the following containers:

• ./log.sh bitcoin Status: Exited (127)

/usr/bin/env: 'bash\r': No such file or directory
/usr/bin/env: use -[v]S to pass options in shebang lines
/usr/bin/env: 'bash\r': No such file or directory
/usr/bin/env: use -[v]S to pass options in shebang lines
/usr/bin/env: 'bash\r': No such file or directory
/usr/bin/env: use -[v]S to pass options in shebang lines
/usr/bin/env: 'bash\r': No such file or directory
/usr/bin/env: use -[v]S to pass options in shebang lines
/usr/bin/env: 'bash\r': No such file or directory
/usr/bin/env: use -[v]S to pass options in shebang lines
/usr/bin/env: 'bash\r': No such file or directory
/usr/bin/env: use -[v]S to pass options in shebang lines

• ./log.sh miner Status: Exited (1)

exec /bin/entrypoint.sh: no such file or directory
exec /bin/entrypoint.sh: no such file or directory
exec /bin/entrypoint.sh: no such file or directory
exec /bin/entrypoint.sh: no such file or directory

• ./log.sh electrs Status: Exited (1)

exec ./entrypoint.sh: no such file or directory
exec ./entrypoint.sh: no such file or directory
exec ./entrypoint.sh: no such file or directory
exec ./entrypoint.sh: no such file or directory
exec ./entrypoint.sh: no such file or directory

• ./log.sh stacks Status: Exited (1)

exec /bin/entrypoint.sh: no such file or directory
exec /bin/entrypoint.sh: no such file or directory
exec /bin/entrypoint.sh: no such file or directory
exec /bin/entrypoint.sh: no such file or directory
exec /bin/entrypoint.sh: no such file or directory

• ./log.sh sbtc Status: Exited (127)

': No such file or directory't execute 'sh
': No such file or directory't execute 'sh
': No such file or directory't execute 'sh
': No such file or directory't execute 'sh
': No such file or directory't execute 'sh

Screenshots or Videos

• Screenshots:

• Video: https://github.com/stacks-network/sbtc/assets/32830427/e8acf4e7-0a24-4cf9-bdb0-e0a2b732b23d

[EmbeddedAndroid]

@alirazacodes would it be possible to try this with WSL2 and docker? I don't believe we support native windows support, as the scripts as you have seen require bash.

[alirazacodes]

@alirazacodes would it be possible to try this with WSL2 and docker? I don't believe we support native windows support, as the scripts as you have seen require bash.

But I'm using git bash here to run the commands and docker is running in the background in Windows OS.

[EmbeddedAndroid]

@alirazacodes would it be possible to try this with WSL2 and docker? I don't believe we support native windows support, as the scripts as you have seen require bash.

But I'm using git bash here to run the commands and docker is running in the background in Windows OS.

Right but all the code in this repo has unix line endings and not DOS.

https://www.cs.toronto.edu/~krueger/csc209h/tut/line-endings.html#:~:text=Text%20files%20created%20on%20DOS,(%22%5Cn%22).

That is why there is the parsing errors you've reported above, even when using git bash since it's not running in a Unix environment.

You can setup docker inside WSL2 - https://docs.docker.com/desktop/wsl/ which will provide you the Unix environment you need.

This issue is valid however, as we don't explicitly state what host requirements are needed, and we will need to address this.

[alirazacodes]

I totally understand.

I'm switching to Mac OS and starting from scratch, which is much more convenient for me than WSL because somehow WSL is breaking on my Windows system.