update go import path and libcontainer

Docker-DCO-1.1-Signed-off-by: Victor Vieux <vieux@docker.com> (github: vieux)

docs/README.md

@@ -5,7 +5,7 @@ Markdown, as implemented by [MkDocs](http://mkdocs.org).
 
 The HTML files are built and hosted on `https://docs.docker.com`, and update
 automatically after each change to the master or release branch of [Docker on
-GitHub](https://github.com/dotcloud/docker) thanks to post-commit hooks. The
+GitHub](https://github.com/docker/docker) thanks to post-commit hooks. The
 `docs` branch maps to the "latest" documentation and the `master` (unreleased
 development) branch maps to the "master" documentation.
 

docs/sources/reference/builder.md

@@ -175,7 +175,7 @@ The cache for `RUN` instructions can be invalidated by `ADD` instructions. See
 
 ### Known Issues (RUN)
 
-- [Issue 783](https://github.com/dotcloud/docker/issues/783) is about file
+- [Issue 783](https://github.com/docker/docker/issues/783) is about file
   permissions problems that can occur when using the AUFS file system. You
   might notice it during an attempt to `rm` a file, for example. The issue
   describes a workaround.

docs/sources/reference/commandline/cli.md

@@ -117,7 +117,7 @@ you can also specify individual sockets too `docker -d -H fd://3`. If the
 specified socket activated files aren't found then docker will exit. 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/).
+https://github.com/docker/docker/blob/master/contrib/init/systemd/socket-activation/).
 
 Docker supports softlinks for the Docker data directory
 (`/var/lib/docker`) and for `/tmp`. TMPDIR and the data directory can be set
@@ -396,9 +396,9 @@ For example:
     A /go
     A /go/src
     A /go/src/github.com
-    A /go/src/github.com/dotcloud
+    A /go/src/github.com/docker
-    A /go/src/github.com/dotcloud/docker
+    A /go/src/github.com/docker/docker
-    A /go/src/github.com/dotcloud/docker/.git
+    A /go/src/github.com/docker/docker/.git
     ....
 
 ## events
@@ -871,7 +871,7 @@ registry or to a self-hosted one.
 
 ### Known Issues (rm)
 
--   [Issue 197](https://github.com/dotcloud/docker/issues/197) indicates
+-   [Issue 197](https://github.com/docker/docker/issues/197) indicates
     that `docker kill` may leave directories behind
     and make it difficult to remove the container.
 
@@ -1008,7 +1008,7 @@ and linking containers.
 
 ### Known Issues (run –volumes-from)
 
-- [Issue 2702](https://github.com/dotcloud/docker/issues/2702):
+- [Issue 2702](https://github.com/docker/docker/issues/2702):
   "lxc-start: Permission denied - failed to mount" could indicate a
   permissions problem with AppArmor. Please see the issue for a
   workaround.

docs/sources/reference/run.md

@@ -86,7 +86,7 @@ and pass along signals. All of that is configurable:
     -i=false        : Keep STDIN open even if not attached
 
 If you do not specify `-a` then Docker will [attach all standard
-streams]( https://github.com/dotcloud/docker/blob/
+streams]( https://github.com/docker/docker/blob/
 75a7f4d90cde0295bcfb7213004abce8d4779b75/commands.go#L1797). You can
 specify to which of the three standard streams (`STDIN`, `STDOUT`,
 `STDERR`) you'd like to connect instead, as in:
@@ -237,7 +237,7 @@ By default, Docker containers are "unprivileged" and cannot, for
 example, run a Docker daemon inside a Docker container. This is because
 by default a container is not allowed to access any devices, but a
 "privileged" container is given access to all devices (see [lxc-template.go](
-https://github.com/dotcloud/docker/blob/master/daemon/execdriver/lxc/lxc_template.go)
+https://github.com/docker/docker/blob/master/daemon/execdriver/lxc/lxc_template.go)
 and documentation on [cgroups devices](
 https://www.kernel.org/doc/Documentation/cgroups/devices.txt)).
 
@@ -262,7 +262,7 @@ If the Docker daemon was started using the `lxc` exec-driver
 (`docker -d --exec-driver=lxc`) then the operator can also specify LXC options
 using one or more `--lxc-conf` parameters. These can be new parameters or
 override existing parameters from the [lxc-template.go](
-https://github.com/dotcloud/docker/blob/master/daemon/execdriver/lxc/lxc_template.go).
+https://github.com/docker/docker/blob/master/daemon/execdriver/lxc/lxc_template.go).
 Note that in the future, a given host's docker daemon may not use LXC, so this
 is an implementation-specific configuration meant for operators already
 familiar with using LXC directly.