Current Behaviour:
When the --interactive flag is passed, the container is run with /bin/bash. However in the course of a normal pipeline run, sh is used though the .bbrun.sh file has it's first line pointing to bash via #!/usr/bin/env bash.
This causes bash specific features like the source command that's used to run a script that doesn't have executable permission to fail (like source venv/bin/activate that's common in python projects)
Expected Behaviour:
Since we already use /bin/bash in the interactive shell, we could use /bin/bash for non-interactive mode script execution as well.
Current Behaviour: When the
--interactiveflag is passed, the container is run with/bin/bash. However in the course of a normal pipeline run,shis used though the.bbrun.shfile has it's first line pointing to bash via#!/usr/bin/env bash. This causes bash specific features like thesourcecommand that's used to run a script that doesn't have executable permission to fail (likesource venv/bin/activatethat's common in python projects)Expected Behaviour: Since we already use
/bin/bashin the interactive shell, we could use/bin/bashfor non-interactive mode script execution as well.