Matt Bentley

Not sure if you missed https://github.com/docker/migrator/issues/109#issuecomment-303496589 but could you try to manually run the curl that is failing? ``` curl -v http://registry.domain.com/v1/search?q= ```

Make sure that you're not running `-e USE_HTTP=true` since according to the output, nginx is running SSL. And it looks like either your v1 registry is not running search or...

https://github.com/docker/docker-registry/blob/master/README.md#search-engine-options >Search-engine options > > The Docker Registry can optionally index repository information in a database for the GET /v1/search endpoint. You can configure the backend with a configuration like:...

Let me do some testing when I get back to my computer and I'll see what I can find out. I have a similar setup with nginx.

Hmm, there is something wrong with the v1 registry then. ``` $ curl -u demo -v https://registry.core.dckrindy.io/v1/search?q= Enter host password for user 'demo': * Trying 192.168.1.50... * TCP_NODELAY set *...

There actually isn't a database for the image data; it is all based on what exists on disk. If you copy the contents from the old to new registry, all...

You mean when the registry image data is stored on disk and the disk is formatted with brtfs, it fails to copy over to the new registry? That doesn't make...

So yeah, that's the problem. `/var/lib/docker` is for local engine storage. The Docker v2 registry image storage is completely different. You would be better off doing a `docker save` and...

Added a test that uses a v2 using `NO_LOGIN`, still need to add a v1 server without auth to test against.

Updated tests to include the following migration scenarios: - v1 to v2 migration with auth - v1 to v2 migration without auth - v1 to DTR - Docker Hub to...