Suggest providing --insecure-registry to docker daemon when push fails
Suggest providing --insecure-registry to docker daemon when push fails

Although docker.Client.push() has an `insecure_registry` parameter,
this has no effect.

If a push fails and the registry had `insecure` set, the solution is
often to provide `--insecure-registry ...` to the docker daemon at
start-up in `/etc/sysconfig/docker` or equivalent.

DBuildService/atomic-reactor,DBuildService/atomic-reactor,jarodwilson/atomic-reactor,projectatomic/atomic-reactor,fr34k8/atomic-reactor,jpopelka/atomic-reactor,jpopelka/atomic-reactor,jarodwilson/atomic-reactor,projectatomic/atomic-reactor,vrutkovs/atomic-reactor,maxamillion/atomic-reactor,fr34k8/atomic-reactor,maxamillion/atomic-reactor,vrutkovs/atomic-reactor