Open ainzlpnoresponse opened 1 year ago
same issue here
I understand that you're facing an issue with starting a Docker container due to the error messages related to the start_services.sh
script. This issue is likely caused by the line endings in the script file. Windows and Linux use different line endings; Windows uses CRLF (Carriage Return, Line Feed), while Linux uses LF (Line Feed).
Docker containers usually run on Linux-based systems, so if your script has Windows line endings, it will cause problems when executed inside the container. To resolve this issue, you need to convert the line endings of the start_services.sh
file to LF.
Many text editors (e.g., Visual Studio Code, Notepad++, Atom) allow you to convert line endings. For example, if you're using Visual Studio Code, you can convert the line endings by following these steps:
start_services.sh
file in Visual Studio Code.CRLF
or LF
indicator in the bottom-right status bar.LF
from the dropdown menu.Save the changes and then try running the docker-compose up --build
command again to see if the issue has been resolved.
I hope this helps!
I am having trouble starting a Docker container using docker-compose. When I run the command docker-compose up --build, the build process finishes successfully, but the container fails to start.
I am using a Dockerfile and a docker-compose.yml file, both of which are located in the root directory of my project. I am running Docker version 20.10.9 on Windows 10.
Can you please help me solve this issue? Any suggestions or advice would be greatly appreciated.
Thank you.