Matt Bentley

The client/server warning is probably because you're running the migrator container; it has a 1.6.2 docker client for backwards compatibility reasons but it isn't a critical warning. The error I...

Can you provide the output of `docker info` from the node where you're attempting the pull? The daemon logs indicate that the insecure registry setting isn't set.

Does the option for `ERROR_ACTION=skip` achieve what you're looking for? That should skip over the image when [pushing or pulling](https://github.com/docker/migrator/blob/master/migrator.sh#L255-L258) or [retagging](https://github.com/docker/migrator/blob/master/migrator.sh#L307-L310).

Thanks for the PR! Sorry for taking so long to get back to you on this. Just a few nits since it is changing the current behavior; I think keeping...

Not currently. I'd have to see if I can use the Docker Hub API to get the images and tags from another namespace. I'd expect so but currently it there...

In order to have it basically do a `docker login` to the registry where it uses HTTP instead of HTTPS, that is all on the engine configuration. The Engine that...

~Are you using `-e USE_INSECURE_CURL=true` in your `docker run` command? That is needed for the curl commands to ignore a certificate that isn't trusted by default.~ Sorry just re-read the...

What sort of authentication is being done on the v1 registry (`V1_REGISTRY`) w/nginx? You have `-e NO_LOGIN=true` so if nginx is taking care of auth, the curl commands aren't going...

If you're using basic auth, you should not be using `-e NO_LOGIN=true`. Did your command change when you created the above output? The code should never get to the `docker...

Whew, ok had me looking for a hole in the code 😄