Deprecate -f flag from docker tag

Closes #9798

@maintainers please note that this is a change to the UX. We no longer
require the -f flag on `docker tag` to move a tag from an existing image.
However, this does make us more consistent across our commands,
see https://github.com/docker/docker/issues/9798 for the history.

Signed-off-by: Doug Davis <dug@us.ibm.com>
master
Doug Davis 2015-12-01 14:02:02 -08:00 committed by Tibor Vass
parent 67eea4d814
commit ecfc3613b2
2 changed files with 0 additions and 5 deletions

View File

@ -14,7 +14,6 @@ parent = "smn_cli"
Tag an image into a repository Tag an image into a repository
-f, --force=false Force the tagging even if there's a conflict
--help=false Print usage --help=false Print usage
You can group your images together using names and tags, and then upload them You can group your images together using names and tags, and then upload them

View File

@ -6,7 +6,6 @@ docker-tag - Tag an image into a repository
# SYNOPSIS # SYNOPSIS
**docker tag** **docker tag**
[**-f**|**--force**[=*false*]]
[**--help**] [**--help**]
IMAGE[:TAG] [REGISTRY_HOST/][USERNAME/]NAME[:TAG] IMAGE[:TAG] [REGISTRY_HOST/][USERNAME/]NAME[:TAG]
@ -18,9 +17,6 @@ If you do not specify a `REGISTRY_HOST`, the command uses Docker's public
registry located at `registry-1.docker.io` by default. registry located at `registry-1.docker.io` by default.
# "OPTIONS" # "OPTIONS"
**-f**, **--force**=*true*|*false*
When set to true, force the alias. The default is *false*.
**--help** **--help**
Print usage statement. Print usage statement.