When developing on Windows you may face issues because of CRLF line endings:

• If core.autocrlf=true is enabled in git (common in Windows), files included in binaries with embed may include CRLF line endings, causing issues when used in docker scenarios.
• If it is disabled, with core.autocrlf=false (usual default), file editors in Windows may add CRLF line endings in files.

With core.autocrlf=input git doesn't include CRLF when checking out files, and it removes the carriage return when commiting files, avoiding the unexpected presence of CRLF line endings.

For example, this issue was found when running the Kibana healthcheck with an elastic-package binary built on Windows:

$ bash -x healthcheck.sh
+ $'\r'
healthcheck.sh: line 2: $'\r': command not found
+ set $'-e\r'
: invalid optionline 3: set: -
...