Skip to content

postgres: Fix incorrect shebang in example initialization script #2568

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 8, 2025

Conversation

reidb1
Copy link
Contributor

@reidb1 reidb1 commented May 8, 2025

The /bin/bash shebang points does not point to the correct path for bash in the container. Because of this, the initialization scripts will not run. Changing to /usr/bin/env bash fixes this problem.

Alternatively /usr/bin/bash would also work.

The `/bin/bash` shebang points does not point to the correct path for bash in the container. Because of this, the initialization scripts will not run. Changing to `/usr/bin/env bash` fixes this problem.

Alternatively `/usr/bin/bash` would also work.
@reidb1 reidb1 changed the title Fix incorrect shebang in example initialization script postgres: Fix incorrect shebang in example initialization script May 8, 2025
Copy link
Member

@tianon tianon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! This is fine, although I'll note that all the images we maintain/support do have a valid /bin/bash, even if it's under a symlink. 🤔

@tianon tianon merged commit 293b60c into docker-library:master May 8, 2025
6 checks passed
@reidb1
Copy link
Contributor Author

reidb1 commented May 8, 2025

Interesting... I ran init scripts with #!/bin/bash and they did not run. ONLY change I made was #!/usr/bin/env bash and they ran...

Maybe there was something else that changed, but I was trying to be careful to make single changes at a time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants