4 ms·
I'd like a service like this, but which I could just SSH to and automatically connect to a fresh Linux instance each time. It seems like it'd be pretty simple
by maddyboo 8y ago
I'd like a service like this, but which I could just SSH to and automatically connect to a fresh Linux instance each time.
It seems like it'd be pretty simple accomplish. You could continually pre-boot a number of Linux containers proportional to the amount of traffic you expect. When a user attempts to connect via SSH, just pop them into the next available instance, FIFO style.
Users could either log in as 'anon' with no password, or they could pick a username and then set up an account just by SCPing their public key, allowing them to persist their instance or save the state for later.
Come to think of it, I basically just described Google Cloud shell, which I really never use, but maybe a lite version with a very simple usage model would be more desirable. I know there's also Docker, but I think the appeal of this idea to me is that I don't need to use any of my local system resources, and I can log in instantly rather than waiting for a container to spin up.
- w7 8y agoHosted https://github.com/Yelp/dockersh https://github.com/Yelp/dockersh might fit your requirements to a degree.
- farisjarrah 8y agoI am not affiliated with RedHat in anyway, but you can set this up very easily on your own with Cockpit by RedHat. Its free as in beer and libre as its under the LGPL licence and gives you basically full access to the machine via a gui. You can view statistics on disk usage, network usage, processes, etc, and can also connect to a terminal in browser with full sudo privileges. Any changes you make in the gui are immediately reflected in the terminal and vice versa. I don't use it for large scale deployments, but its perfect for managing personal systems. I even have a docker extension set up on it and I can search and set up docker images right there from the gui. Fun and easy way to test out new software
- jlgaddis 8y agoI wouldn't think it would be too difficult to coerce [x]inetd to spawn a new container -- instead of a daemon -- and connect you to it.