'build.sh build' completed successfully without errors, unable to run

[Jugrnot]

As stated in title, was able to successfully run './build.sh build' without errors, however I'm unable to run even just ./build.sh successfully now, attempting to run with 'git bash' on Win10; output is the following:

Spent a fair amount of time attempting to figure out how to get my python path associated with /usr/bin/env, but despite my hour long google search, I'm not able to figure it out. Also attempted to create a .bashrc and add "export PATH=/c/Users/elesj/AppData/Local/Programs/Python/Python38-32/python:$PATH"

The strange part is, a simple test python script I can run from bash:

Windows 10 22H2
Docker Desktop 4.30.0
python 3.8.1
git 2.38.0

[fboulnois]

My guess is your docker-entrypoint.py is using CRLF Windows line endings \r\n, instead of LF Unix line endings \n , which is causing the script to fail to run. If you have the file command installed you can check this by running file docker-entrypoint.py. The solution is to switch back to Unix file endings.

[Jugrnot]

My guess is your docker-entrypoint.py is using CRLF Windows line endings \r\n, instead of LF Unix line endings \n , which is causing the script to fail to run. If you have the file command installed you can check this by running file docker-entrypoint.py. The solution is to switch back to Unix file endings.

So I ran: vim docker-entrypoint.py -c "set ff=unix" -c ":wq"
Then attempted to run: ./build.sh run 'Andromeda galaxy in a bottle'
Which resulted in sitting at a blinking cursor for 2 hours doing nothing before my PC went to sleep. Zero GPU or CPU usage noted. I had to reboot for another issue, and now we're back to square one:

[fboulnois]

It's not clear if you ran the ./build.sh build command beforehand again to rebuild the Docker container. If you did do so and are still experiencing issues, I don't have any other specific recommendations. Local installations of Python do not interact with the Docker container at all, so that is unlikely to be the cause of the issue.

[Jugrnot]

It's not clear if you ran the ./build.sh build command beforehand again to rebuild the Docker container. If you did do so and are still experiencing issues, I don't have any other specific recommendations. Local installations of Python do not interact with the Docker container at all, so that is unlikely to be the cause of the issue.

I have no legitimate reason as to why, but I in fact did re-run the build command. Any suggestion on maybe wiping the entire thing including the docker container out and starting from scratch given the development of needing unix line endings?