Update to libcontainer 8d1d0ba38a7348c5cfdc05aea3b

This fixes issues where the apparmor profile is not applied to processes
via docker exec.  As a side effect the parent processes were unable to
kill the additional child processes because of the profile mismatch.

Easy way to reproduce on an apparmor system:
docker run -ti debian:jessie bash
ps auxZ
- look at the labels

- in another shell
docker exec <name> sleep 1000

- go back to the first container and
ps auxZ
- make sure all processes have the correct docker-default profile

Signed-off-by: Michael Crosby <crosbymichael@gmail.com>
Merge pull request #8552 from crosbymichael/update-libcontainer-oct2

Update to libcontainer 8d1d0ba38a7348c5cfdc05aea3b
Fix builder from being over-aggressive on ${}

`${SOME_VAR%pattern}` was turning into `SOME_VAL%pattern}` which the shell would then balk at.

I've updated the `TOKEN_ENV_INTERPOLATION` regex to account for this (ie, if `${` is used, it _must_ also match the closing `}`), and renamed the variable to not be exported (since it's not used outside the function following it).

I also added comments for the bits of `tokenEnvInterpolation` so they're easier to follow. :smile:

Signed-off-by: Andrew Page <admwiggin@gmail.com>
Merge pull request #8553 from tianon/fix-over-aggressive-shell-interpolation-regex

Fix builder from being over-aggressive on ${}
docs: Fix some minor typos on dockerlinks guide

Signed-off-by: Fabio Rehm <fgrehm@gmail.com>
Merge pull request #8558 from fgrehm/patch-4

docs: Fix some minor typos on dockerlinks guide
Remove client key.json generation for trust

This removes the key generation for trust from main while it is not
being consumed.  The problem is that because this is being set in main
if a user runs as root initially the files will be owned by root.  Later
if the user sets up the docker group they are unable to read the keys.
This is half a user error and documentation problem and the other half
is management.

We decided to remove this code for now while it is not being used and
will revisit it later when the consuming features are added.  A few
options are to generate lazily and provide a clear error message on an
EPERM so that the user knows what is wrong and can correct the
permissions.

Signed-off-by: Michael Crosby <crosbymichael@gmail.com>
Merge pull request #8563 from crosbymichael/remove-key-create

Remove client key.json generation for trust
change docs.docker.io to docs.docker.com in install script

Signed-off-by: Tibor Vass <teabee89@gmail.com>
Merge pull request #8564 from tiborvass/remove-docker-dot-io

change docs.docker.io to docs.docker.com in install script