From e47d4b8506e990c3f466676a1108de1d1b7ece40 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Martin=20Andr=C3=A9?= <m.andre@redhat.com>
Date: Wed, 14 Oct 2015 09:36:30 +0900
Subject: [PATCH] Cleanup outdated documentation
Kolla implements a workaround for the referenced docker issue. There is
no need to document it, however still recommend installing a recent
kernel for better compatibility.
Change-Id: I06eaa0bb0980f0698202724f523ab08cb344418e
---
doc/deploy-all-in-one-node.rst | 14 +-------------
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git a/doc/deploy-all-in-one-node.rst b/doc/deploy-all-in-one-node.rst
index 04f62780da..d154c246c3 100644
--- a/doc/deploy-all-in-one-node.rst
+++ b/doc/deploy-all-in-one-node.rst
@@ -17,22 +17,11 @@ The machine recommended requirements:
- more than 8gb main memory.
- at least 40gb disk space.
-To verify the Ubuntu kernel is sufficient to operate Kolla, run the command:
-
-::
-
- docker run -i -t --net=host ubuntu su
-
-If the command displays "su: System error",
-the system suffers from this DockerBug_. This is a possible way to solve the issue:
-
-::
+It is generally a good idea to run a recent kernel. On Ubuntu LTS::
sudo apt-get install linux-image-generic-lts-vivid
sudo reboot
-
-
The guide assumes that you have build images using the following command.
::
@@ -81,4 +70,3 @@ a local private registry on gigabit networks.
.. _DeployingRegistryServer: https://docs.docker.com/registry/deploying/
-.. _DockerBug: https://github.com/docker/docker/issues/5899