-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
To Reproduce Steps to reproduce the behavior:
- Run a diip CI job that uses tmux sessions and sets HOME=
- While the job is running open a tmux window on the host machine
- Any tmux sessions started while the above window will ignore the HOME env variable
Expected behavior
- HOME should be respected
Bug impact
- CI jobs running inconsistently when tmux is already running on the Host
Known workaround
- Close all tmux sessions
More info
When instructlab_home_dir is configured in RhelAIBootcContainer, the HOME environment variable is not consistently set for tmux sessions created via exec_command_with_tmux. This occurs because:
-
- RhelAIBootcContainer.exec_command overrides the base method to prepend HOME={self.home_dir} && to all commands when instructlab_home_dir is configured
- tmux server only inherits environment variables when it is first started
- If a tmux server is already running from a previous session, subsequent tmux new-session commands ignore the HOME environment variable set by the command prefix
- This leads to inconsistent behavior where HOME is only set correctly if no previous tmux session was running