Describe the bug
A clear and concise description of what the bug is.
It seems the post-install commands are called with bash -l when using clr-installer --config ... in the live-server installer - this creates a new bash login shell, which in turns triggers .bash_login if it exists - I have a modified live-server image which has the .bash_login in the roots home directory, so it's getting called again, which isn't functional as the script it calls requires input from the user, so halting the post-install script without any means of interaction
To Reproduce
Steps to reproduce the behavior:
- Create a custom live-iso which has a
.bash_login inside the root home directory which requests users input
- Use a config with a post-install command
- call
clr-installer with your config
- See it hang indefinitely
Expected behavior
A clear and concise description of what you expected to happen.
I expected it to be called with just bash not bash -l, so to execute normally
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
- Clear Linux OS Version: [swupd info] 42210
- Installer Version [clr-installer -v] 2.7.11
- Platform: [hardware infomation] N/A
Additional context
Add any other context about the problem here.
Describe the bug
A clear and concise description of what the bug is.
It seems the
post-installcommands are called withbash -lwhen usingclr-installer --config ...in the live-server installer - this creates a new bash login shell, which in turns triggers.bash_loginif it exists - I have a modifiedlive-serverimage which has the.bash_loginin the roots home directory, so it's getting called again, which isn't functional as the script it calls requires input from the user, so halting thepost-installscript without any means of interactionTo Reproduce
Steps to reproduce the behavior:
.bash_logininside the root home directory which requests users inputclr-installerwith your configExpected behavior
A clear and concise description of what you expected to happen.
I expected it to be called with just
bashnotbash -l, so to execute normallyScreenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.