Skip to content
This repository has been archived by the owner on Sep 7, 2022. It is now read-only.

"/bin/bash^M: bad interpreter: No such file or directory" #104

Closed
Zeniere opened this issue Aug 29, 2022 · 1 comment
Closed

"/bin/bash^M: bad interpreter: No such file or directory" #104

Zeniere opened this issue Aug 29, 2022 · 1 comment

Comments

@Zeniere
Copy link

Zeniere commented Aug 29, 2022

entrypoint.sh is using CRLF instead of LF for new lines
@Zeniere Zeniere changed the title "/bin/bash^M: bad interpreter: No such file or directory" entrypoint.sh using CRLF instead of LF gives "/bin/bash^M: bad interpreter: No such file or directory" Aug 29, 2022
@hlky
Copy link

hlky commented Aug 29, 2022 •
edited
Loading

This was fixed, pull the repo.

I just checked to confirm, entrypoint.sh is currently using LF

@hlky hlky closed this as completed Aug 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Zeniere @hlky