Bug: `initializer` container fails with `env: 'bash\r': No such file or directory` when running docker compose

[amairiya]

When running DefectDojo using the provided docker-compose.yml, the initializer container fails to start due to a shebang parsing error.

The container exits with the following error:

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

This prevents the initializer service from completing successfully and blocks the rest of the services (uwsgi, celeryworker, celerybeat) from starting.

---

Steps to Reproduce

1. Clone the repository
2. Run:

docker compose up

3. Observe container logs

---

Actual Behavior

The initializer container exits with code 127.

initializer-1  | env: 'bash\r': No such file or directory
initializer-1  | env: use -[v]S to pass options in shebang lines
initializer-1 exited with code 127

Container django-defectdojo-initializer-1 Error
service "initializer" didn't complete successfully: exit 127

---

Expected Behavior

The initializer container should successfully initialize the database and exit normally, allowing the dependent services (uwsgi, celeryworker, celerybeat) to start.

---

Environment

• Docker version: <your docker version>
• Docker Compose version: <your compose version>
• OS: <Linux / WSL / Windows / macOS>
• DefectDojo version: latest
• Installation method: Docker Compose

---

Possible Cause

It appears that one or more entrypoint scripts contain Windows CRLF line endings, resulting in the shebang being interpreted as:

#!/usr/bin/env bash\r

[valentijnscholten]

Looks like you're using windows? Please make sure to checkout without converting line endings locally: https://docs.github.com/en/get-started/git-basics/configuring-git-to-handle-line-endings

PR #14448 will help windows users as it enforces this.

[valentijnscholten]

Let us know how it goes, closing for now.