As suggested by @metalivedev
Docker-DCO-1.1-Signed-off-by: Brandon Philips <brandon.philips@coreos.com> (github: philips)
| ... | ... |
@@ -63,10 +63,10 @@ the ``-H`` flag for the client. |
| 63 | 63 |
# both are equal |
| 64 | 64 |
|
| 65 | 65 |
|
| 66 |
-To run the daemon with `systemd socket activation <http://0pointer.de/blog/projects/socket-activation.html>`, use ``docker -d -H fd://``. |
|
| 66 |
+To run the daemon with `systemd socket activation <http://0pointer.de/blog/projects/socket-activation.html>`_, use ``docker -d -H fd://``. |
|
| 67 | 67 |
Using ``fd://`` will work perfectly for most setups but you can also specify individual sockets too ``docker -d -H fd://3``. |
| 68 | 68 |
If the specified socket activated files aren't found then docker will exit. |
| 69 |
-You can find examples of using systemd socket activation with docker and systemd in the `docker source tree <https://github.com/dotcloud/docker/blob/master/contrib/init/systemd/socket-activation/>`. |
|
| 69 |
+You can find examples of using systemd socket activation with docker and systemd in the `docker source tree <https://github.com/dotcloud/docker/blob/master/contrib/init/systemd/socket-activation/>`_. |
|
| 70 | 70 |
|
| 71 | 71 |
.. _cli_attach: |
| 72 | 72 |
|