Revert doc changes from #9652

Because the patch is not in 1.4, the v1.16 docs shouldn't have been
updated. Docs were promoted to v1.17 by #9742.

Signed-off-by: Arnaud Porterie <arnaud.porterie@docker.com>
Error should be 409 as the container is different state to remove

Closes #9569

Signed-off-by: Srini Brahmaroutu <srbrahma@us.ibm.com>
registry: remove accidentally added --insecure-registry feature

If `--insecure-registry mydomain.com` was specified, it would match a registry at mydomain.com on any port.
This was accidentally added in #9735 and is now being reverted.

Signed-off-by: Tibor Vass <teabee89@gmail.com>
Clarify preferred btrfs-progs dependency and fix some minor inconsistencies

Signed-off-by: Andrew "Tianon" Page <admwiggin@gmail.com>
Fixing ValidateTagName error message

Signed-off-by: Don Kjer <don.kjer@gmail.com>
Enable test-integration-cli for Windows platform

Signed-off-by: Arnaud Porterie <arnaud.porterie@docker.com>
Move per-container forward rules to DOCKER chain

Docker-DCO-1.1-Signed-off-by: Ian Bishop <ianbishop@pace7.com> (github: porjo)
Create DOCKER forward chain on driver init

Docker-DCO-1.1-Signed-off-by: Ian Bishop <ianbishop@pace7.com> (github: porjo)
Create tests for pkg/iptables

Docker-DCO-1.1-Signed-off-by: Ian Bishop <ianbishop@pace7.com> (github: porjo)
Update networking.md with new iptables behaviour

Docker-DCO-1.1-Signed-off-by: Ian Bishop <ianbishop@pace7.com> (github: porjo)
Tidy driver.go/LinkContainers

Docker-DCO-1.1-Signed-off-by: Ian Bishop <ianbishop@pace7.com> (github: porjo)
bump Go to 1.4

Signed-off-by: Cristian Staretu <cristian.staretu@gmail.com>
Reinstall standard library with netgo

Fixes #9449

Signed-off-by: Alexander Morozov <lk4d4@docker.com>
Fix TestBuildWithTabs for go 1.4

Signed-off-by: Alexander Morozov <lk4d4@docker.com>
start new API v1.17 docs

Signed-off-by: Jean-Tiare Le Bigot <jt@yadutaf.fr>
Improve error message for conflicting container name.

This changes the error message that is returned by the daemon when
a container-name already exists.

The old message suggests that containers can be renamed, which is
currently not possible.

To prevent confusion, the part "(or rename)" is removed from
the error-message.

Message before this change;

    FATA[0000] Error response from daemon: Conflict, The name foobar is already assigned to 728ac36fb0ab. You have to delete (or rename) that container to be able to assign foobar to a container again.

Message after this change;

    FATA[0000] Error response from daemon: Conflict. The name 'foobar' is already in use by container 728ac36fb0ab. You have to delete that container to be able to reuse that name.

Relates to: https://github.com/docker/docker/issues/3036

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Merge pull request #9742 from yadutaf/master

Start new API v1.17 docs
Merge pull request #9284 from icecrime/client_only_integration_tests

Enable test-integration-cli for Windows platform
Merge pull request #9750 from icecrime/9652_revert_doc

Revert doc changes from #9652
Merge pull request #7003 from porjo/6034-fowardChain

Move per-container forward rules to DOCKER chain