Error updating service, does not exist or it is not available when using a duplicate registry

[sabady]

Hi,
I have a private Harbor registry which is duplicated.
Both are load balanced and accessible via CLI.

When I attempt a jump from the main to the secondary Harbor, Shepherd fails with the errors:
no such manifest; Error updating service; Image <image_name> does not exist or it is not available.

Manual docker pull is successful.

Jumping back to the main Harbor does not fix the issue.

Restarting the service with update --force does not help.
Running docker stack deploy --prune --with-registry-auth -c docker-compose.yml also not helpful.

compose version: 3.8
service config:
shepherd:
image: mazzolino/shepherd:latest
logging: scalable-logging
deploy:
replicas: 1
placement:
constraints:
- "node.role==manager"
hostname: shepherd-updater
environment:
- SLEEP_TIME=5m
- BLACKLIST_SERVICES=dev_shepherd dev_nginx telemetry_
- WITH_REGISTRY_AUTH=true
- FILTER_SERVICES=label=autoupdate
- IMAGE_AUTOCLEAN_LIMIT=3
- TZ=UTC
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
- /home/core/.docker/config.json:/root/.docker/config.json:ro

[djmaze]

@sabady Sorry for the late answer. I don't know about Harbor and what it means to "jump" between instances. You deployed your services using the image from the secondary instance then? If that is the case and you are logged into the secondary registry as your core user, it should work, according to your configuration here.

[djmaze]

Closing for now because no further feedback.