Reference `docker exec` in "Running a command in an existing container" section #168

Closed
johnpancoast opened this Issue Nov 21, 2014 · 3 comments

Projects

None yet

3 participants

@johnpancoast

I'm new to docker so I could definitely be missing something but couldn't the Running a command in an existing container section reference the docker exec command?

@endersonmaia
Contributor

I've sent a PR for removing even ssh in favor of docker exec, see #161

Yes, you could provide another PR with just the added content for docker exec.

docker exec is only available from >= 1.3, and Docker is evolving very fast, and it's hard to keep everything up to date!

@johnpancoast

Docker is evolving very fast, and it's hard to keep everything up to date!

Figured that was the case!

@FooBarWidget
Member

Sorry responding so late, we're at small team at Phusion and it's been way too busy the past few months. I've finally come around to investigating docker exec.

I've found that docker exec is just a thin wrapper around nsenter, though with a few changes. Most of the usual cons of nsenter still applies. Therefore, I think it's not a good idea to remove SSH entirely in favor of docker exec. What we can do is replacing nsenter with docker exec, and disabling SSH by default. I've begun work on this.

@FooBarWidget FooBarWidget added this to the 0.9.16 milestone Jan 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment