[Request]: container machine run should spawn a login shell

[jurisevo]

Feature or enhancement request details

Default behaviour of container machine run is to spawn an interactive shell inside container machine. Help info on container machine run --help even states following:

ARGUMENTS:
  <executable>            Command to run (default: login shell)

My observed behaviour is that interactive shell spawned is not a login shell. This has a number of drawbacks how interactive shell is initialised (both bash and zsh will not source "profile" rc files). This is in contrast to say connection via SSH to a running machine instances.

I would argue that shell should be login shells, or at least there should be a way to configure this per container machine.

container CLI version 1.0.0 (build: release, commit: ee848e3)

Code of Conduct

• I agree to follow this project's Code of Conduct

[Dave861]

I reproduced this on current main (6e65319). The default shell is interactive but doesn’t source ~/.profile; running sh -l in the same machine does. I’m going to work on a focused fix and regression test.