Re:Podman v4.6 Introduces Podmansh: A Revolutionary Login Shell
by 5e92cb50239222b on Sunday August 13, 2023 @05:43AM
(#37108280)
Have you looked at toolbox? it might already be doing what you want — it's a thin wrapper around podman that integrates containers with the rest of the system — you don't really even feel that you're running a container.
Re:Podman v4.6 Introduces Podmansh: A Revolutionary Login Shell
by maffydub on Sunday August 13, 2023 @07:19AM
(#37108851)
Have you tried floki (https://github.com/Metaswitch/floki) - this is what we use to solve this problem.
Re:Podman v4.6 Introduces Podmansh: A Revolutionary Login Shell
by Chris660 on Sunday August 13, 2023 @08:20AM
(#37109258)
In addition to the other suggestions, you might want to check-out distrobox:
https://github.com/89luca89/distrobox
It provides support for starting host commands within a container, and also exporting commands from containers to the host.
Re:Podman v4.6 Introduces Podmansh: A Revolutionary Login Shell
by yencabulator on Sunday August 13, 2023 @04:55PM
(#37114363)
Last I looked, distrobox made $HOME fully accessible to all its containers. That's the very opposite of parent comment's "protect against the most trivial of supply chain attacks".
Re:Podman v4.6 Introduces Podmansh: A Revolutionary Login Shell
by salawat on Sunday August 13, 2023 @11:21AM
(#37110815)
Thin client is one answer to your question. Running a shell to a server results in significantly longer endurance for a client on battery than otherwise. Not swamping your system's I/O bus is another. OS incompat. Regulatory shenanigans.
Then there's also the training angle. I've found nothing quite as tangibly gets the visceral sense of computing across like walking a junior through a "where are your bits now?" now exercise with a handful of physical boxen.
Not really sure what one would use a login shell for, though. I mean, if I, as the user, am merely logging into a containerized shell, why don't I execute the container locally? Why use SSH? Sure, the volumes mounted into the login shell container might contain data I need, but one could also simply mount them as network storage locally.