docker/cli
1
0
Fork 0
mirror of https://github.com/docker/cli.git synced 2026-01-16 20:22:36 +03:00
Code Activity

Merge pull request #8516 from jamtur01/sshd

Browse Source 
Minor changes to SSHd example
Upstream-commit: 69e3a55560df06a23cc74ba54badf120e5271bf9
Component: engine
This commit is contained in:
Fred Lifton
2014-10-16 15:44:10 -07:00
parent cde87628c0 67eb2ed955
commit a2918879a4
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
components/engine/docs/sources/examples/running_ssh_service.md
View File

@@ -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``.
@@ -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