Skip to content

Commit

Permalink
Minor changes to SSHd example
Browse files Browse the repository at this point in the history
Docker-DCO-1.1-Signed-off-by: James Turnbull <james@lovedthanlost.net> (github: jamtur01)
  • Loading branch information
jamtur01 committed Oct 11, 2014
1 parent 7fa7c42 commit f1c319f
Showing 1 changed file with 6 additions and 5 deletions.
11 changes: 6 additions & 5 deletions docs/sources/examples/running_ssh_service.md
Expand Up @@ -46,7 +46,8 @@ the container's port 22 is mapped to:

And now you can ssh as `root` on the container's IP address (you can find it
with `docker inspect`) or on port `49154` of the Docker daemon's host IP address
(`ip address` or `ifconfig` can tell you that):
(`ip address` or `ifconfig` can tell you that) or `localhost` if on the
Docker daemon host:

$ ssh root@192.168.1.2 -p 49154
# The password is ``screencast``.
Expand All @@ -55,15 +56,15 @@ with `docker inspect`) or on port `49154` of the Docker daemon's host IP address
## Environment variables

Using the `sshd` daemon to spawn shells makes it complicated to pass environment
variables to the user's shell via the simple Docker mechanisms, as `sshd` scrubs
variables to the user's shell via the normal Docker mechanisms, as `sshd` scrubs
the environment before it starts the shell.

If you're setting values in the Dockerfile using `ENV`, you'll need to push them
to a shell initialisation file like the `/etc/profile` example in the Dockerfile
If you're setting values in the `Dockerfile` using `ENV`, you'll need to push them
to a shell initialization file like the `/etc/profile` example in the `Dockerfile`
above.

If you need to pass`docker run -e ENV=value` values, you will need to write a
short script to do the same before you start `sshd -D` - and then replace the
short script to do the same before you start `sshd -D` and then replace the
`CMD` with that script.

## Clean up
Expand Down

0 comments on commit f1c319f

Please sign in to comment.