From 4d6a232fc092aa58e049feb35c918ed096f0c080 Mon Sep 17 00:00:00 2001 From: Antonio Murdaca Date: Mon, 29 Feb 2016 13:40:45 +0100 Subject: [PATCH] Revert "resolve the config file from the sudo user" This reverts commit afde6450ee7bd4a43765fdc0a9799b411276d9e4. Signed-off-by: Antonio Murdaca --- docs/reference/commandline/cli.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/reference/commandline/cli.md b/docs/reference/commandline/cli.md index 95a3c07bb6..96486d73d9 100644 --- a/docs/reference/commandline/cli.md +++ b/docs/reference/commandline/cli.md @@ -78,9 +78,6 @@ For example: Instructs Docker to use the configuration files in your `~/testconfigs/` directory when running the `ps` command. -> **Note**: If you run docker commands with `sudo`, Docker first looks for a configuration -> file in `/root/.docker/`, before looking in `~/.docker/` for the user that did the sudo call. - Docker manages most of the files in the configuration directory and you should not modify them. However, you *can modify* the `config.json` file to control certain aspects of how the `docker`