Closed tbugfinder closed 5 years ago
verbose output:
VERBOSE Registry: <accountid>.dkr.ecr.<region>.amazonaws.com
VERBOSE Namespace: <folder>
VERBOSE Repo Name: <name>
VERBOSE Repo Tag: <repotag>
VERBOSE Version: None
VERBOSE Obtaining tags: https://<accountid>.dkr.ecr.<region>.amazonaws.com/v2/<folder>/<name>/tags/list
DEBUG GET https://<accountid>.dkr.ecr.<region>.amazonaws.com/v2/<folder>/<name>/tags/list
DEBUG Http Error with code 401
DEBUG update_token: challenge = 'Basic realm="https://<accountid>.dkr.ecr.<region>.amazonaws.com/",service="ecr.amazonaws.com"'
ERROR Unrecognized authentication challenge, exiting.
Cleaning up...
ERROR: pulling container failed!
Also failed using sregistry "client" https://github.com/singularityhub/sregistry-cli/issues/145
@bauerm97 Are there any plans to support a private docker registry with authentication?
seems to be fixed with ~3.1.x (didn't test 3.0.x though).
Version of Singularity:
2.6.0-dist
Expected behavior
singularity pull
should pull images from AWS ECR successfully.Actual behavior
singularity pull
fails with error messageERROR Unrecognized authentication challenge, exiting.
. I've configured SINGULARITY_DOCKER_PASSWORD and SINGULARITY_DOCKER_USERNAME with output ofaws ecr get-login --no-include-email
.Steps to reproduce behavior
SINGULARITY_DOCKER_PASSWORD
andSINGULARITY_DOCKER_USERNAME
singularity pull docker://< aws ecr >/