Windows Docker setup: docker compose up fails due to CRLF line endings in executable scripts

[Debajeet-1411]

Hi everyone,

I'm setting up the Open Library development environment on Windows using Docker Desktop and followed the official setup guide.

During setup I consistently ran into an issue where docker compose up -d failed because the Solr container exited with status code 127.

The relevant log was:

/opt/solr/docker/scripts/docker-entrypoint.sh: line 48:
/docker/ol-local-solr-start.sh: cannot execute: required file not found

After some debugging, I found that the shell scripts under the docker/ directory had been checked out with CRLF line endings (Git's default behavior on Windows with core.autocrlf=true).

Converting those scripts from CRLF to LF allowed the Solr container to start successfully.

I then encountered a similar issue with executable Python scripts:

env: 'python\r': No such file or directory

which was also resolved by converting the relevant scripts to LF line endings.

At this point, most of the Docker services are running, but I'm still investigating application-level issues (Infobase connectivity and all routes returning 404s), so I'm not yet sure whether those are expected for a fresh development setup or are related.

Before opening a GitHub issue, I wanted to ask:

• Is this CRLF behavior already a known Windows issue?
• Is there an existing recommendation or fix (for example, via .gitattributes) to ensure executable scripts are always checked out with LF?
• Has anyone else experienced this on a fresh Windows setup?

If it's a reproducible issue, I'd be happy to open an issue or submit a PR to improve the Windows setup documentation.

Thanks!