Sfoglia il codice sorgente

Update MTU work-around to use the new -mtu flag

Brian Dorsey 11 anni fa
parent
commit
cdd14b1a31
1 ha cambiato i file con 5 aggiunte e 6 eliminazioni
  1. 5 6
      docs/sources/installation/google.rst

+ 5 - 6
docs/sources/installation/google.rst

@@ -57,18 +57,17 @@
     docker-playground:~$ curl get.docker.io | bash
     docker-playground:~$ sudo update-rc.d docker defaults
 
-7. Start a new container:
+7. If running in zones: us-central1-a, europe-west1-1, and europe-west1-b, the docker daemon must be started with the `-mtu` flag. Without the flag, you may experience intermittent network pauses. 
+`See this issue <https://code.google.com/p/google-compute-engine/issues/detail?id=57>`_ for more details.
 
 .. code-block:: bash
 
-    docker-playground:~$ sudo docker run busybox echo 'docker on GCE \o/'
-    docker on GCE \o/
+    docker -d -mtu 1460
 
-**The -lxc-conf flag below is required** when running docker images in zones: us-central1-a, europe-west1-1, and europe-west1-b. Without the MTU flag, you may experience intermittent network pauses. 
-`See this issue <https://code.google.com/p/google-compute-engine/issues/detail?id=57>`_ for more details.
+8. Start a new container:
 
 .. code-block:: bash
 
-    docker-playground:~$ sudo docker run -lxc-conf="lxc.network.mtu = 1460" busybox echo 'docker on GCE \o/'
+    docker-playground:~$ sudo docker run busybox echo 'docker on GCE \o/'
     docker on GCE \o/