Open jampy opened 6 years ago
Since your v1 is just using http, you need to use the V1_USE_HTTP option. Check the README for instructions on how to use that as it also involves making sure you have a dameon option set.
Both registries are behind a reverse Proxy, so accessing them using HTTPS is correct.
In fact, you can see the migrator
request (GET /v2/
) hits the registry.
Ah so I misinterpreted what you meant by:
I'm using the FQDN of the v1 registry, without https://
With you running such a new engine, it looks like you're hitting this: https://docs.docker.com/engine/deprecated/#interacting-with-v1-registries
v1 registry interaction has been deprecated per this comment:
Starting with Docker 17.12, support for V1 registries has been removed, and the --disable-legacy-registry flag can no longer be used, and dockerd will fail to start when set.
To perform the migration, you will want to install an older engine version.
On a machine with Debian 9.5 and
docker-ce 18.06.1~ce~3-0~debian
just installed, I am not able to login the V1 registry. It seems the migrator is accessing the old registry via the v2 protocol...So, it's trying to access
/v2/
.I'm using the FQDN of the v1 registry, without
https://
.The v1 registry is running
registry:0.9.1
. I can see the request made by themigrator
:The same happens when I try to do
docker login
(with a up-to-date client), but I guess that's normal as new clients need a v2 registry...What am I doing wrong?