Can't setup replication between harbor and an ECS registry

[arthurzenika]

We're trying to setup a replication between our harbor installation and and ECS registry.

ECS registry comes with a predefined password that you can get through aws cli with aws ecr get-login --no-include-email --region eu-west-1 the user is AWS and the password is pretty long (in this case 1916 characters long), I don't think there is a way to change it since it's generated by AWS.

When using the "test connection" button we get a " Failed to ping endpoint." error message on the web interface. "failed to ping target" from the API.

When we remove the https:// from the URL I think it tries in http and times out (which probably leaked the above password over clear text communication - or not if port 80 is not listening which seems to be the case for AWS ECS - this is probably another issue).

Then when we try to save the endpoint anyway we get " Invalid endpoint name. " in the web interface. We tried to understand what was wrong with the name (but it was a simple string "ECS"). Looking at the API response we see "password max length is 48". https://github.com/vmware/harbor/blob/64cc71ea12acff7d0f5179bcbd0c346a0aa256a6/src/common/models/replication_job.go#L103-L107 seems to be the culprit.

So this in my opinion is a double bug :

• displayed error is wrong
• can't replicate with a registry that has a long password

[steven-zou]

@arthurlogilab

So far, harbor does not support replicating images to any harbor instance.

[steven-zou]

@arthurlogilab we have the plan to support in future releases.

Agreed – "integration" with other registries is something we've definitely talked about and there have been a few issues where similar topics have been discussed.

@arthurlogilab Can you share your use case here? Are you simply hoping to replication to / from an external registry, or is there something else you're hoping to accomplish?

[arthurzenika]

@clouderati yes it's pretty simple, we have a jenkins building docker images, pushing to harbor and we would like harbor to push to ECS to have a mirror of that registry to be used by applications on AWS, the application also runs nearer to harbor which is in a different zone.

Thanks @arthurlogilab – totally reasonable use case. Let's keep this open to track this request.

PRs welcomed. 😄

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[arthurzenika]

We still have this problem, thanks for not marking it as stale.