Dockersh – a shell that puts users into individual docker containers

> This allows you to have a single ssh process on the normal ssh port which places user sessions into their own individual docker containers in a secure and locked down manor.

Funniest instance of this misused homonym I've seen.

I'm not sure if this is related -- because it doesn't require Docker or Linux -- but I've got a small shell tool for transparent development on remote machines. Gives you the ability to do something similiar (`ws shell`), and drop directly into the remote environment you're working in.

I use it to work on my Mac, but develop on a Linux box:

https://github.com/matadon/workspace

With a name like that I hope the patron saint of Dockersh is Sean Connery

To shamelessly plug a much more minimalist solution, https://github.com/polydawn/siphon-cli can also give you new shells shells inside existing containers (or whatever; it's more like screen than anything tightly bound to docker).

Siphon does nothing but create and forward psuedoterminals, so it has a lot less features to directly interact with docker than dockersh appears to have, but it's also able to do its job without root or any priviledged syscalls, and doesn't rely on any knowledge of kernel namespaces at all. Which is more useful may depend on your perspective and usecases.

Interesting. I'll take some time to learn it over the weekend. Right now at work I use the following solution to keep a shell running on containers:

https://gist.github.com/TeMPOraL/3d134ce0d4a2b2f4232b

Basically, it starts a screen instance with a shell and your script running side by side, so when you Docker-attach to it, you can C-a " to shell.

run.sh would be the script you want to be run in container - the one that starts your webserver, database, whatever.

I adapted a screen solution from some random StackOverflow comment.

Pretty similar to libvirt sandbox (done about 4 years ago):

http://sandbox.libvirt.org/quickstart/

Libvirt sandbox can also put processes, jobs, users etc into real VMs as well as chroots ^W containers.

I'm not sure if any shell hosting providers post here. I operate one of the companies in this space since 2001.

This is a fun alternative to proper jails but unfortunately, security wise this would not last very long on in a real world application.

Not going to lie, would be pretty cool to set something like this up and auto provision upon payment.

I've been using Firejail for this purpose:

http://l3net.wordpress.com/2014/04/16/how-to-restrict-a-logi...

I don't get it :/

> This allows you to have a single ssh process on the normal ssh port which places user sessions into their own individual docker containers in a secure and locked down manner.

No! Warning!

Docker is not secure and locked down. Do not use this for "security".