From a208c5d1d7673bae937d2fc40767a72a7df230b1 Mon Sep 17 00:00:00 2001 From: "Hongli Lai (Phusion)" Date: Tue, 12 Nov 2013 13:18:07 +0100 Subject: [PATCH] Add SSH instructions --- README.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/README.md b/README.md index aafcc97..4dd947c 100644 --- a/README.md +++ b/README.md @@ -92,6 +92,26 @@ Here's an example showing you how to a memached server runit entry can be made. Note that the shell script must run the daemon **without letting it daemonize/fork it**. Usually, daemons provide a command line flag or a config file option for that. +### Login in to the container + +You can use SSH to login to any container that is based on baseimage-docker. + +Start a container based on baseimage-docker (or a container based on an image based on baseimage-docker): + + docker run phusion/baseimage + +Find out the ID of the container that you just ran: + + docker ps + +Once you have the ID, look for its IP address with: + + docker inspect | grep IPAddress + +Now SSH into the container. In this example we're using [the default insecure key](https://github.com/phusion/baseimage-docker/blob/master/image/insecure_key), but if you're followed the instructions well then you've already replaced that with your own key. You did replace the key, didn't you? + + ssh -i insecure_key root@ + ## Building the image yourself If for whatever reason you want to build the image yourself instead of downloading it from the Docker registry, follow these instructions.