3 ms·
I wouldn't call that revolutionary. As far as I understand, this is a simple alias to something like `podman exec -it somecontainer bash`. We were able to do th
by ximm 3y ago
I wouldn't call that revolutionary. As far as I understand, this is a simple alias to something like `podman exec -it somecontainer bash`. We were able to do this for a long time. I mean, it is nice that they provide a simple alias for that. But the marketing talk is a bit much for my taste.
- choppaface 3y agoThe feature is more similar to e.g. dockersh than just exec https://github.com/Yelp/dockersh https://github.com/Yelp/dockersh Or e.g. change ssh config to use ForceCommand. That said, the main benefit is not just that a shell gets a container but that you can easily compose this feature with the container / image ecosystem to deploy specialized shells. Perhaps even you don’t need a VM to service the request but rather a container orchestrator ..
- nvarsj 3y agoI don’t think that’s what podmansh does. Instead it’s a system replacement shell. Nothing to do with your running containers. Instead it seems to let you sandbox users on your VM/baremetal to a container.