From 12b8e799c7b0e57f79d3f5d8e95a8e6e86fcc3f7 Mon Sep 17 00:00:00 2001 From: Amal <56926487+amalkurup89@users.noreply.github.com> Date: Wed, 3 Jun 2020 23:51:11 +0530 Subject: [PATCH] Typo fixture (#10950) * Typo fixture * Minor typo fix * Typo fix --- engine/install/index.md | 2 +- engine/security/userns-remap.md | 2 +- machine/drivers/linode.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/engine/install/index.md b/engine/install/index.md index 1eb1eff1a6..b767a86d4e 100644 --- a/engine/install/index.md +++ b/engine/install/index.md @@ -122,7 +122,7 @@ These builds allow for testing from the latest code on the master branch. ## Support Docker Engine releases of a year-month branch are supported with patches as -needed for one month after the the next year-month general availability release. +needed for one month after the next year-month general availability release. This means bug reports and backports to release branches are assessed until the end-of-life date. diff --git a/engine/security/userns-remap.md b/engine/security/userns-remap.md index 7e6e9363ad..36145d46d2 100644 --- a/engine/security/userns-remap.md +++ b/engine/security/userns-remap.md @@ -245,7 +245,7 @@ for some of these limitations. To disable user namespaces for a specific container, add the `--userns=host` flag to the `docker container create`, `docker container run`, or `docker container exec` command. -There is a side effect when using this flag: user remapping will not be enabled for that container but, because the read-only (image) layers are shared between containers, ownership of the the containers filesystem will still be remapped. +There is a side effect when using this flag: user remapping will not be enabled for that container but, because the read-only (image) layers are shared between containers, ownership of the containers filesystem will still be remapped. What this means is that the whole container filesystem will belong to the user specified in the `--userns-remap` daemon config (`231072` in the example above). This can lead to unexpected behavior of programs inside the container. For instance `sudo` (which checks that its binaries belong to user `0`) or binaries with a `setuid` flag. diff --git a/machine/drivers/linode.md b/machine/drivers/linode.md index 82279d759d..e5d5f6f7bc 100644 --- a/machine/drivers/linode.md +++ b/machine/drivers/linode.md @@ -44,7 +44,7 @@ See the [Linode Docker machine driver project page](https://github.com/linode/do | `linode-stackscript` | `LINODE_STACKSCRIPT` | None | Specifies the Linode StackScript to use to create the instance, either by numeric ID, or using the form *username*/*label*. | `linode-stackscript-data` | `LINODE_STACKSCRIPT_DATA` | None | A JSON string specifying data that is passed (via UDF) to the selected StackScript. | `linode-create-private-ip` | `LINODE_CREATE_PRIVATE_IP` | None | A flag specifying to create private IP for the Linode instance. -| `linode-tags` | `LINODE_TAGS` | None | A comma separated list of tags to apply to the the Linode resource +| `linode-tags` | `LINODE_TAGS` | None | A comma separated list of tags to apply to the Linode resource | `linode-ua-prefix` | `LINODE_UA_PREFIX` | None | Prefix the User-Agent in Linode API calls with some 'product/version' #### Notes