From b3b0caa0d0df177b49013389da63e8ff4fdb61eb Mon Sep 17 00:00:00 2001 From: Mark Gurevich Date: Mon, 2 May 2016 17:26:20 -0400 Subject: [PATCH] Fix readthedocs build error --- .../docker/dockerized_xcat/run_xcat_in_docker_compose.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/source/advanced/docker/dockerized_xcat/run_xcat_in_docker_compose.rst b/docs/source/advanced/docker/dockerized_xcat/run_xcat_in_docker_compose.rst index f5039b4f5..b934a0ce8 100644 --- a/docs/source/advanced/docker/dockerized_xcat/run_xcat_in_docker_compose.rst +++ b/docs/source/advanced/docker/dockerized_xcat/run_xcat_in_docker_compose.rst @@ -146,9 +146,10 @@ To update the xCAT Docker image, you can run :: Known Issues ------------ -.. [1] When you start up xCAT Docker container, you might see an error message at the end of the output like: :: +.. [1] +When you start up xCAT Docker container, you might see an error message at the end of the output like: :: - "Couldn't connect to Docker daemon at http+unix://var/run/docker.sock - is it running? If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable." + Couldn't connect to Docker daemon at http+unix://var/run/docker.sock - is it running? If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.` - You can ignore it, the container has already been running. It is a Docker bug `#1214 `_ +You can ignore it, the container has already been running. It is a Docker bug `#1214 `_