@@ -26,7 +26,7 @@ corresponding to existing containers.

 To figure out where your control groups are mounted, you can run:

-    grep cgroup /proc/mounts

+    $ grep cgroup /proc/mounts

 ## Enumerating Cgroups

@@ -287,7 +287,7 @@ an interface) can do some serious accounting.

 For instance, you can setup a rule to account for the outbound HTTP

 traffic on a web server:

-    iptables -I OUTPUT -p tcp --sport 80

+    $ iptables -I OUTPUT -p tcp --sport 80

 There is no `-j` or `-g` flag,

 so the rule will just count matched packets and go to the following

@@ -295,7 +295,7 @@ rule.

 Later, you can check the values of the counters, with:

-    iptables -nxvL OUTPUT

+    $ iptables -nxvL OUTPUT

 Technically, `-n` is not required, but it will

 prevent iptables from doing DNS reverse lookups, which are probably

@@ -337,11 +337,11 @@ though.

 The exact format of the command is:

-    ip netns exec <nsname> <command...>

+    $ ip netns exec <nsname> <command...>

 For example:

-    ip netns exec mycontainer netstat -i

+    $ ip netns exec mycontainer netstat -i

 `ip netns` finds the "mycontainer" container by

 using namespaces pseudo-files. Each process belongs to one network

@@ -369,14 +369,13 @@ measure network usage. From there, you can examine the pseudo-file named

 control group (i.e. in the container). Pick any one of them.

 Putting everything together, if the "short ID" of a container is held in

-the environment variable `$CID`, then you can do

-this:

-

-    TASKS=/sys/fs/cgroup/devices/$CID*/tasks

-    PID=$(head -n 1 $TASKS)

-    mkdir -p /var/run/netns

-    ln -sf /proc/$PID/ns/net /var/run/netns/$CID

-    ip netns exec $CID netstat -i

+the environment variable `$CID`, then you can do this:

+

+    $ TASKS=/sys/fs/cgroup/devices/$CID*/tasks

+    $ PID=$(head -n 1 $TASKS)

+    $ mkdir -p /var/run/netns

+    $ ln -sf /proc/$PID/ns/net /var/run/netns/$CID

+    $ ip netns exec $CID netstat -i

 ## Tips for high-performance metric collection

@@ -32,8 +32,8 @@ Again, you can do it in other ways but you need to do more work.

 ## Check out the Source

-    git clone http://git@github.com/dotcloud/docker

-    cd docker

+    $ git clone http://git@github.com/dotcloud/docker

+    $ cd docker

 To checkout a different revision just use `git checkout`

 with the name of branch or revision number.

@@ -45,7 +45,7 @@ Dockerfile in the current directory. Essentially, it will install all

 the build and runtime dependencies necessary to build and test Docker.

 This command will take some time to complete when you first execute it.

-    sudo make build

+    $ sudo make build

 If the build is successful, congratulations! You have produced a clean

 build of docker, neatly encapsulated in a standard build environment.

@@ -54,7 +54,7 @@ build of docker, neatly encapsulated in a standard build environment.

 To create the Docker binary, run this command:

-    sudo make binary

+    $ sudo make binary

 This will create the Docker binary in `./bundles/<version>-dev/binary/`

@@ -65,7 +65,7 @@ The binary is available outside the container in the directory

 host docker executable with this binary for live testing - for example,

 on ubuntu:

-    sudo service docker stop ; sudo cp $(which docker) $(which docker)_ ; sudo cp ./bundles/<version>-dev/binary/docker-<version>-dev $(which docker);sudo service docker start

+    $ sudo service docker stop ; sudo cp $(which docker) $(which docker)_ ; sudo cp ./bundles/<version>-dev/binary/docker-<version>-dev $(which docker);sudo service docker start

 > **Note**: 

 > Its safer to run the tests below before swapping your hosts docker binary.

@@ -74,7 +74,7 @@ on ubuntu:

 To execute the test cases, run this command:

-    sudo make test

+    $ sudo make test

 If the test are successful then the tail of the output should look

 something like this

@@ -105,11 +105,10 @@ something like this

     PASS

     ok      github.com/dotcloud/docker/utils        0.017s

-If $TESTFLAGS is set in the environment, it is passed as extra

-arguments to `go test`. You can use this to select certain tests to run,

-eg.

+If $TESTFLAGS is set in the environment, it is passed as extra arguments

+to `go test`. You can use this to select certain tests to run, e.g.

-    TESTFLAGS=`-run \^TestBuild\$` make test

+    $ TESTFLAGS=`-run \^TestBuild\$` make test

 If the output indicates "FAIL" and you see errors like this:

@@ -124,7 +123,7 @@ is recommended.

 You can run an interactive session in the newly built container:

-    sudo make shell

+    $ sudo make shell

     # type 'exit' or Ctrl-D to exit

@@ -134,7 +133,7 @@ If you want to read the documentation from a local website, or are

 making changes to it, you can build the documentation and then serve it

 by:

-    sudo make docs

+    $ sudo make docs

     # when its done, you can point your browser to http://yourdockerhost:8000

     # type Ctrl-C to exit

@@ -95,7 +95,7 @@ your container with the docker build command, e.g.

 Start the container with `apache2` and `sshd` running and managed, forwarding

 a port to our SSH instance:

-    docker run -p 127.0.0.1:222:22 -d managed_image "/usr/sbin/sshd" "/etc/init.d/apache2 start"

+    $ docker run -p 127.0.0.1:222:22 -d managed_image "/usr/sbin/sshd" "/etc/init.d/apache2 start"

 We now clearly see one of the benefits of the cfe-docker integration: it

 allows to start several processes as part of a normal `docker run` command.

@@ -20,28 +20,28 @@ different versions of CouchDB on the same data, etc.

 Note that we're marking `/var/lib/couchdb` as a data volume.

-    COUCH1=$(sudo docker run -d -p 5984 -v /var/lib/couchdb shykes/couchdb:2013-05-03)

+    $ COUCH1=$(sudo docker run -d -p 5984 -v /var/lib/couchdb shykes/couchdb:2013-05-03)

 ## Add data to the first database

 We're assuming your Docker host is reachable at `localhost`. If not,

 replace `localhost` with the public IP of your Docker host.

-    HOST=localhost

-    URL="http://$HOST:$(sudo docker port $COUCH1 5984 | grep -Po '\d+$')/_utils/"

-    echo "Navigate to $URL in your browser, and use the couch interface to add data"

+    $ HOST=localhost

+    $ URL="http://$HOST:$(sudo docker port $COUCH1 5984 | grep -Po '\d+$')/_utils/"

+    $ echo "Navigate to $URL in your browser, and use the couch interface to add data"

 ## Create second database

 This time, we're requesting shared access to `$COUCH1`'s volumes.

-    COUCH2=$(sudo docker run -d -p 5984 --volumes-from $COUCH1 shykes/couchdb:2013-05-03)

+    $ COUCH2=$(sudo docker run -d -p 5984 --volumes-from $COUCH1 shykes/couchdb:2013-05-03)

 ## Browse data on the second database

-    HOST=localhost

-    URL="http://$HOST:$(sudo docker port $COUCH2 5984 | grep -Po '\d+$')/_utils/"

-    echo "Navigate to $URL in your browser. You should see the same data as in the first database"'!'

+    $ HOST=localhost

+    $ URL="http://$HOST:$(sudo docker port $COUCH2 5984 | grep -Po '\d+$')/_utils/"

+    $ echo "Navigate to $URL in your browser. You should see the same data as in the first database"'!'

 Congratulations, you are now running two Couchdb containers, completely

 isolated from each other *except* for their data.

@@ -80,7 +80,7 @@ continue to do this until we stop it.

 **Steps:**

-    CONTAINER_ID=$(sudo docker run -d ubuntu /bin/sh -c "while true; do echo hello world; sleep 1; done")

+    $ CONTAINER_ID=$(sudo docker run -d ubuntu /bin/sh -c "while true; do echo hello world; sleep 1; done")

 We are going to run a simple hello world daemon in a new container made

 from the `ubuntu` image.

@@ -98,7 +98,7 @@ from the `ubuntu` image.

 <!-- -->

-    sudo docker logs $container_id

+    $ sudo docker logs $container_id

 Check the logs make sure it is working correctly.

@@ -107,7 +107,7 @@ Check the logs make sure it is working correctly.

 <!-- -->

-    sudo docker attach --sig-proxy=false $container_id

+    $ sudo docker attach --sig-proxy=false $container_id

 Attach to the container to see the results in real-time.

@@ -120,7 +120,7 @@ Attach to the container to see the results in real-time.

 Exit from the container attachment by pressing Control-C.

-    sudo docker ps

+    $ sudo docker ps

 Check the process list to make sure it is running.

@@ -128,7 +128,7 @@ Check the process list to make sure it is running.

 <!-- -->

-    sudo docker stop $container_id

+    $ sudo docker stop $container_id

 Stop the container, since we don't need it anymore.

@@ -137,7 +137,7 @@ Stop the container, since we don't need it anymore.

 <!-- -->

-    sudo docker ps

+    $ sudo docker ps

 Make sure it is really stopped.

@@ -21,7 +21,7 @@ apt source and installs the database software on Ubuntu.

 Create an empty file called Dockerfile:

-    touch Dockerfile

+    $ touch Dockerfile

 Next, define the parent image you want to use to build your own image on

 top of. Here, we'll use [Ubuntu](https://index.docker.io/_/ubuntu/)

@@ -69,21 +69,21 @@ container.

 Now, lets build the image which will go through the

 Dockerfile we made and run all of the commands.

-    sudo docker build -t <yourname>/mongodb .

+    $ sudo docker build -t <yourname>/mongodb .

 Now you should be able to run `mongod` as a daemon

 and be able to connect on the local port!

     # Regular style

-    MONGO_ID=$(sudo docker run -d <yourname>/mongodb)

+    $ MONGO_ID=$(sudo docker run -d <yourname>/mongodb)

     # Lean and mean

-    MONGO_ID=$(sudo docker run -d <yourname>/mongodb --noprealloc --smallfiles)

+    $ MONGO_ID=$(sudo docker run -d <yourname>/mongodb --noprealloc --smallfiles)

     # Check the logs out

-    sudo docker logs $MONGO_ID

+    $ sudo docker logs $MONGO_ID

     # Connect and play around

-    mongo --port <port you get from `docker ps`>

+    $ mongo --port <port you get from `docker ps`>

 Sweet!

@@ -134,16 +134,16 @@ Go to the directory that has your `Dockerfile` and run the following command

 to build a Docker image. The `-t` flag let's you tag your image so it's easier

 to find later using the `docker images` command:

-    sudo docker build -t <your username>/centos-node-hello .

+    $ sudo docker build -t <your username>/centos-node-hello .

 Your image will now be listed by Docker:

-    sudo docker images

+    $ sudo docker images

-    > # Example

-    > REPOSITORY                 TAG       ID              CREATED

-    > centos                     6.4       539c0211cd76    8 weeks ago

-    > gasi/centos-node-hello     latest    d64d3505b0d2    2 hours ago

+    # Example

+    REPOSITORY                 TAG       ID              CREATED

+    centos                     6.4       539c0211cd76    8 weeks ago

+    gasi/centos-node-hello     latest    d64d3505b0d2    2 hours ago

 ## Run the image

@@ -151,44 +151,44 @@ Running your image with `-d` runs the container in detached mode, leaving the

 container running in the background. The `-p` flag redirects a public port to

 a private port in the container. Run the image you previously built:

-    sudo docker run -p 49160:8080 -d <your username>/centos-node-hello

+    $ sudo docker run -p 49160:8080 -d <your username>/centos-node-hello

 Print the output of your app:

     # Get container ID

-    sudo docker ps

+    $ sudo docker ps

     # Print app output

-    sudo docker logs <container id>

+    $ sudo docker logs <container id>

-    > # Example

-    > Running on http://localhost:8080

+    # Example

+    Running on http://localhost:8080

 ## Test

 To test your app, get the the port of your app that Docker mapped:

-    sudo docker ps

+    $ sudo docker ps

-    > # Example

-    > ID            IMAGE                          COMMAND              ...   PORTS

-    > ecce33b30ebf  gasi/centos-node-hello:latest  node /src/index.js         49160->8080

+    # Example

+    ID            IMAGE                          COMMAND              ...   PORTS

+    ecce33b30ebf  gasi/centos-node-hello:latest  node /src/index.js         49160->8080

 In the example above, Docker mapped the `8080` port of the container to `49160`.

 Now you can call your app using `curl` (install if needed via:

 `sudo apt-get install curl`):

-    curl -i localhost:49160

+    $ curl -i localhost:49160

-    > HTTP/1.1 200 OK

-    > X-Powered-By: Express

-    > Content-Type: text/html; charset=utf-8

-    > Content-Length: 12

-    > Date: Sun, 02 Jun 2013 03:53:22 GMT

-    > Connection: keep-alive

-    >

-    > Hello World

+    HTTP/1.1 200 OK

+    X-Powered-By: Express

+    Content-Type: text/html; charset=utf-8

+    Content-Length: 12

+    Date: Sun, 02 Jun 2013 03:53:22 GMT

+    Connection: keep-alive

+    

+    Hello World

 We hope this tutorial helped you get up and running with Node.js and

 CentOS on Docker. You can get the full source code at

@@ -125,14 +125,14 @@ prompt, you can create a table and populate it.

     psql (9.3.1)

     Type "help" for help.

-    docker=# CREATE TABLE cities (

+    $ docker=# CREATE TABLE cities (

     docker(#     name            varchar(80),

     docker(#     location        point

     docker(# );

     CREATE TABLE

-    docker=# INSERT INTO cities VALUES ('San Francisco', '(-194.0, 53.0)');

+    $ docker=# INSERT INTO cities VALUES ('San Francisco', '(-194.0, 53.0)');

     INSERT 0 1

-    docker=# select * from cities;

+    $ docker=# select * from cities;

          name      | location

     ---------------+-----------

      San Francisco | (-194,53)

@@ -143,7 +143,7 @@ prompt, you can create a table and populate it.

 You can use the defined volumes to inspect the PostgreSQL log files and

 to backup your configuration and data:

-    docker run -rm --volumes-from pg_test -t -i busybox sh

+    $ docker run -rm --volumes-from pg_test -t -i busybox sh

     / # ls

     bin      etc      lib      linuxrc  mnt      proc     run      sys      usr

@@ -29,7 +29,7 @@ image.

 Next we build an image from our `Dockerfile`.

 Replace `<your username>` with your own user name.

-    sudo docker build -t <your username>/redis .

+    $ sudo docker build -t <your username>/redis .

 ## Run the service

@@ -42,7 +42,7 @@ Importantly, we're not exposing any ports on our container. Instead

 we're going to use a container link to provide access to our Redis

 database.

-    sudo docker run --name redis -d <your username>/redis

+    $ sudo docker run --name redis -d <your username>/redis

 ## Create your web application container

@@ -52,19 +52,19 @@ created with an alias of `db`. This will create a secure tunnel to the

 `redis` container and expose the Redis instance running inside that

 container to only this container.

-    sudo docker run --link redis:db -i -t ubuntu:12.10 /bin/bash

+    $ sudo docker run --link redis:db -i -t ubuntu:12.10 /bin/bash

 Once inside our freshly created container we need to install Redis to

 get the `redis-cli` binary to test our connection.

-    apt-get update

-    apt-get -y install redis-server

-    service redis-server stop

+    $ apt-get update

+    $ apt-get -y install redis-server

+    $ service redis-server stop

 As we've used the `--link redis:db` option, Docker

 has created some environment variables in our web application container.

-    env | grep DB_

+    $ env | grep DB_

     # Should return something similar to this with your values

     DB_NAME=/violet_wolf/db

@@ -79,13 +79,13 @@ with `DB`. The `DB` comes from the link alias specified when we launched

 the container. Let's use the `DB_PORT_6379_TCP_ADDR` variable to connect to

 our Redis container.

-    redis-cli -h $DB_PORT_6379_TCP_ADDR

-    redis 172.17.0.33:6379>

-    redis 172.17.0.33:6379> set docker awesome

+    $ redis-cli -h $DB_PORT_6379_TCP_ADDR

+    $ redis 172.17.0.33:6379>

+    $ redis 172.17.0.33:6379> set docker awesome

     OK

-    redis 172.17.0.33:6379> get docker

+    $ redis 172.17.0.33:6379> get docker

     "awesome"

-    redis 172.17.0.33:6379> exit

+    $ redis 172.17.0.33:6379> exit

 We could easily use this or other environment variables in our web

 application to make a connection to our `redis`

@@ -19,7 +19,7 @@ Riak pre-installed.

 Create an empty file called Dockerfile:

-    touch Dockerfile

+    $ touch Dockerfile

 Next, define the parent image you want to use to build your image on top

 of. We'll use [Ubuntu](https://index.docker.io/_/ubuntu/) (tag:

@@ -126,7 +126,7 @@ Populate it with the following program definitions:

 Now you should be able to build a Docker image for Riak:

-    docker build -t "<yourname>/riak" .

+    $ docker build -t "<yourname>/riak" .

 ## Next steps

@@ -99,13 +99,13 @@ launches.

 We can now build our new container.

-    sudo docker build -t <yourname>/supervisord .

+    $ sudo docker build -t <yourname>/supervisord .

 ## Running our Supervisor container

 Once We've got a built image we can launch a container from it.

-    sudo docker run -p 22 -p 80 -t -i <yourname>/supervisord

+    $ sudo docker run -p 22 -p 80 -t -i <yourname>/supervisord

     2013-11-25 18:53:22,312 CRIT Supervisor running as root (no user in config file)

     2013-11-25 18:53:22,312 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing

     2013-11-25 18:53:22,342 INFO supervisord started with pid 1

@@ -60,8 +60,8 @@ have not done so before.

 There is a systemd service unit created for docker. To start the docker

 service:

-    sudo systemctl start docker

+    $ sudo systemctl start docker

 To start on system boot:

-    sudo systemctl enable docker

+    $ sudo systemctl enable docker

@@ -46,8 +46,8 @@ Linux kernel (it even builds on OSX!).

 ## Get the docker binary:

-    wget https://get.docker.io/builds/Linux/x86_64/docker-latest -O docker

-    chmod +x docker

+    $ wget https://get.docker.io/builds/Linux/x86_64/docker-latest -O docker

+    $ chmod +x docker

 > **Note**:

 > If you have trouble downloading the binary, you can also get the smaller

@@ -58,7 +58,7 @@ Linux kernel (it even builds on OSX!).

 ## Run the docker daemon

     # start the docker in daemon mode from the directory you unpacked

-    sudo ./docker -d &

+    $ sudo ./docker -d &

 ## Giving non-root access

@@ -87,16 +87,16 @@ all the client commands.

 To upgrade your manual installation of Docker, first kill the docker

 daemon:

-    killall docker

+    $ killall docker

 Then follow the regular installation steps.

 ## Run your first container!

     # check your docker version

-    sudo ./docker version

+    $ sudo ./docker version

     # run a container and open an interactive shell in the container

-    sudo ./docker run -i -t ubuntu /bin/bash

+    $ sudo ./docker run -i -t ubuntu /bin/bash

 Continue with the [*Hello World*](/examples/hello_world/#hello-world) example.

@@ -39,24 +39,24 @@ do so via:

 Download the `httpup` file to

 `/etc/ports/`:

-    curl -q -o - http://crux.nu/portdb/?a=getup&q=prologic > /etc/ports/prologic.httpup

+    $ curl -q -o - http://crux.nu/portdb/?a=getup&q=prologic > /etc/ports/prologic.httpup

 Add `prtdir /usr/ports/prologic` to

 `/etc/prt-get.conf`:

-    vim /etc/prt-get.conf

+    $ vim /etc/prt-get.conf

     # or:

-    echo "prtdir /usr/ports/prologic" >> /etc/prt-get.conf

+    $ echo "prtdir /usr/ports/prologic" >> /etc/prt-get.conf

 Update ports and prt-get cache:

-    ports -u

-    prt-get cache

+    $ ports -u

+    $ prt-get cache

 To install (*and its dependencies*):

-    prt-get depinst docker

+    $ prt-get depinst docker

 Use `docker-bin` for the upstream binary or

 `docker-git` to build and install from the master

@@ -70,20 +70,20 @@ and Docker Daemon to work properly.

 Please read the `README.rst`:

-    prt-get readme docker

+    $ prt-get readme docker

 There is a `test_kernel_config.sh` script in the

 above ports which you can use to test your Kernel configuration:

-    cd /usr/ports/prologic/docker

-    ./test_kernel_config.sh /usr/src/linux/.config

+    $ cd /usr/ports/prologic/docker

+    $ ./test_kernel_config.sh /usr/src/linux/.config

 ## Starting Docker

 There is a rc script created for Docker. To start the Docker service:

-    sudo su -

-    /etc/rc.d/docker start

+    $ sudo su -

+    $ /etc/rc.d/docker start

 To start on system boot:

@@ -30,35 +30,35 @@ report](https://bugzilla.redhat.com/show_bug.cgi?id=1043676) filed for

 it. To proceed with `docker-io` installation on Fedora 19, please remove

 `docker` first.

-    sudo yum -y remove docker

+    $ sudo yum -y remove docker

 For Fedora 20 and later, the `wmdocker` package will

 provide the same functionality as `docker` and will

 also not conflict with `docker-io`.

-    sudo yum -y install wmdocker

-    sudo yum -y remove docker

+    $ sudo yum -y install wmdocker

+    $ sudo yum -y remove docker

 Install the `docker-io` package which will install

 Docker on our host.

-    sudo yum -y install docker-io

+    $ sudo yum -y install docker-io

 To update the `docker-io` package:

-    sudo yum -y update docker-io

+    $ sudo yum -y update docker-io

 Now that it's installed, let's start the Docker daemon.

-    sudo systemctl start docker

+    $ sudo systemctl start docker

 If we want Docker to start at boot, we should also:

-    sudo systemctl enable docker

+    $ sudo systemctl enable docker

 Now let's verify that Docker is working.

-    sudo docker run -i -t fedora /bin/bash

+    $ sudo docker run -i -t fedora /bin/bash

 **Done!**, now continue with the [*Hello

 World*](/examples/hello_world/#hello-world) example.

@@ -49,8 +49,8 @@ is all that is needed.

 There is a systemd service unit created for Docker. To start Docker as

 service:

-    sudo systemctl start lxc-docker

+    $ sudo systemctl start lxc-docker

 To start on system boot:

-    sudo systemctl enable lxc-docker

+    $ sudo systemctl enable lxc-docker

@@ -43,7 +43,7 @@ use flags to pull in the proper dependencies of the major storage

 drivers, with the "device-mapper" use flag being enabled by default,

 since that is the simplest installation path.

-    sudo emerge -av app-emulation/docker

+    $ sudo emerge -av app-emulation/docker

 If any issues arise from this ebuild or the resulting binary, including

 and especially missing kernel configuration flags and/or dependencies,

@@ -61,18 +61,18 @@ and/or AUFS, depending on the storage driver you`ve decided to use).

 To start the docker daemon:

-    sudo /etc/init.d/docker start

+    $ sudo /etc/init.d/docker start

 To start on system boot:

-    sudo rc-update add docker default

+    $ sudo rc-update add docker default

 ### systemd

 To start the docker daemon:

-    sudo systemctl start docker.service

+    $ sudo systemctl start docker.service

 To start on system boot:

-    sudo systemctl enable docker.service

+    $ sudo systemctl enable docker.service

@@ -45,19 +45,19 @@ page_keywords: Docker, Docker documentation, installation, google, Google Comput

 <!-- -->

     $ gcutil ssh docker-playground

-    docker-playground:~$

+    $ docker-playground:~$

 5.  Install the latest Docker release and configure it to start when the

     instance boots:

 <!-- -->

-    docker-playground:~$ curl get.docker.io | bash

-    docker-playground:~$ sudo update-rc.d docker defaults

+    $ docker-playground:~$ curl get.docker.io | bash

+    $ docker-playground:~$ sudo update-rc.d docker defaults

 6.  Start a new container:

 <!-- -->

-    docker-playground:~$ sudo docker run busybox echo 'docker on GCE \o/'

-    docker on GCE \o/

+    $ docker-playground:~$ sudo docker run busybox echo 'docker on GCE \o/'

+    $ docker on GCE \o/

@@ -40,7 +40,7 @@ image that is used for the job.

 If you are using Homebrew on your machine, simply run the following

 command to install `boot2docker`:

-    brew install boot2docker

+    $ brew install boot2docker

 #### Manual installation

@@ -49,13 +49,13 @@ Open up a new terminal window, if you have not already.

 Run the following commands to get boot2docker:

     # Enter the installation directory

-    cd ~/bin

+    $ cd ~/bin

     # Get the file

-    curl https://raw.github.com/boot2docker/boot2docker/master/boot2docker > boot2docker

+    $ curl https://raw.github.com/boot2docker/boot2docker/master/boot2docker > boot2docker

     # Mark it executable

-    chmod +x boot2docker

+    $ chmod +x boot2docker

 ### Docker OS X Client

@@ -67,25 +67,25 @@ The `docker` daemon is accessed using the

 Run the following command to install the `docker`

 client:

-    brew install docker

+    $ brew install docker

 #### Manual installation

 Run the following commands to get it downloaded and set up:

     # Get the docker client file

-    DIR=$(mktemp -d ${TMPDIR:-/tmp}/dockerdl.XXXXXXX) && \

-    curl -f -o $DIR/ld.tgz https://get.docker.io/builds/Darwin/x86_64/docker-latest.tgz && \

-    gunzip $DIR/ld.tgz && \

-    tar xvf $DIR/ld.tar -C $DIR/ && \

-    cp $DIR/usr/local/bin/docker ./docker

+    $ DIR=$(mktemp -d ${TMPDIR:-/tmp}/dockerdl.XXXXXXX) && \

+    $ curl -f -o $DIR/ld.tgz https://get.docker.io/builds/Darwin/x86_64/docker-latest.tgz && \

+    $ gunzip $DIR/ld.tgz && \

+    $ tar xvf $DIR/ld.tar -C $DIR/ && \

+    $ cp $DIR/usr/local/bin/docker ./docker

     # Set the environment variable for the docker daemon

-    export DOCKER_HOST=tcp://127.0.0.1:4243

+    $ export DOCKER_HOST=tcp://127.0.0.1:4243

     # Copy the executable file

-    sudo mkdir -p /usr/local/bin

-    sudo cp docker /usr/local/bin/

+    $ sudo mkdir -p /usr/local/bin

+    $ sudo cp docker /usr/local/bin/

 And that's it! Let's check out how to use it.

@@ -97,13 +97,13 @@ Inside the `~/bin` directory, run the following

 commands:

     # Initiate the VM

-    ./boot2docker init

+    $ ./boot2docker init

     # Run the VM (the docker daemon)

-    ./boot2docker up

+    $ ./boot2docker up

     # To see all available commands:

-    ./boot2docker

+    $ ./boot2docker

     # Usage ./boot2docker {init|start|up|pause|stop|restart|status|info|delete|ssh|download}

@@ -113,7 +113,7 @@ Once the VM with the `docker` daemon is up, you can

 use the `docker` client just like any other

 application.

-    docker version

+    $ docker version

     # Client version: 0.7.6

     # Go version (client): go1.2

     # Git commit (client): bc3b2ec

@@ -137,7 +137,7 @@ interact with our containers as if they were running locally:

 If you feel the need to connect to the VM, you can simply run:

-    ./boot2docker ssh

+    $ ./boot2docker ssh

     # User: docker

     # Pwd:  tcuser

@@ -154,7 +154,7 @@ See the GitHub page for

 ### If SSH complains about keys:

-    ssh-keygen -R '[localhost]:2022'

+    $ ssh-keygen -R '[localhost]:2022'

 ### Upgrading to a newer release of boot2docker

@@ -162,9 +162,9 @@ To upgrade an initialised VM, you can use the following 3 commands. Your

 persistence disk will not be changed, so you won't lose your images and

 containers:

-    ./boot2docker stop

-    ./boot2docker download

-    ./boot2docker start

+    $ ./boot2docker stop

+    $ ./boot2docker download

+    $ ./boot2docker start

 ### About the way Docker works on Mac OS X:

@@ -30,14 +30,14 @@ To proceed with Docker installation please add the right Virtualization

 repository.

     # openSUSE 12.3

-    sudo zypper ar -f http://download.opensuse.org/repositories/Virtualization/openSUSE_12.3/ Virtualization

+    $ sudo zypper ar -f http://download.opensuse.org/repositories/Virtualization/openSUSE_12.3/ Virtualization

     # openSUSE 13.1

-    sudo zypper ar -f http://download.opensuse.org/repositories/Virtualization/openSUSE_13.1/ Virtualization

+    $ sudo zypper ar -f http://download.opensuse.org/repositories/Virtualization/openSUSE_13.1/ Virtualization

 Install the Docker package.

-    sudo zypper in docker

+    $ sudo zypper in docker

 It's also possible to install Docker using openSUSE's1-click install.

 Just visit [this](http://software.opensuse.org/package/docker) page,

@@ -47,17 +47,17 @@ the docker package.

 Now that it's installed, let's start the Docker daemon.

-    sudo systemctl start docker

+    $ sudo systemctl start docker

 If we want Docker to start at boot, we should also:

-    sudo systemctl enable docker

+    $ sudo systemctl enable docker

 The docker package creates a new group named docker. Users, other than

 root user, need to be part of this group in order to interact with the