You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently podmansh is using the hard-coded /bin/sh shell, however there are use cases where people might want to have a different shell.
A possible solution would be to link /bin/sh to the desired user shell, e.g. /bin/fish but that would likely break a good portion of shell scripts that require or use #!/bin/sh. Therefore the configuration of at least the shell for podmansh would make sense.
Suggest potential solution
Introduce a new podmansh section in containers.conf that allows users to configure the various parameters used by podmansh:
Shell
Container name
Timeout
Have you considered any alternatives?
I tried to use environment variables but that appeared a bit clumsy to me.
I also tried to use container labels but they are not user-configurable options.
A new configuration section allows users to set their preferred shell via ~/.config/containers/containers.conf.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Feature request description
Currently
podmansh
is using the hard-coded/bin/sh
shell, however there are use cases where people might want to have a different shell.A possible solution would be to link
/bin/sh
to the desired user shell, e.g./bin/fish
but that would likely break a good portion of shell scripts that require or use#!/bin/sh
. Therefore the configuration of at least the shell for podmansh would make sense.Suggest potential solution
Introduce a new
podmansh
section incontainers.conf
that allows users to configure the various parameters used by podmansh:Have you considered any alternatives?
I tried to use environment variables but that appeared a bit clumsy to me.
I also tried to use container labels but they are not user-configurable options.
A new configuration section allows users to set their preferred shell via
~/.config/containers/containers.conf
.Additional context
No response
The text was updated successfully, but these errors were encountered: