I need help to get Singularity to work with AWS ECR container (Docker) images.
I am using this pattern:
I am properly logged into Docker and can pull the image with Docker pull. However, leveraging the password in SINGULARITY_DOCKER_PASSWORD gives me:
[...]
*** STARTING DOCKER IMPORT PYTHON ****
DEBUG Docker layers and metadata will be written to: /tmp/.singularity-layers.MljARLQ9
VERBOSE2 SINGULARITY_DOCKER_USERNAME found as AWS
VERBOSE2 SINGULARITY_DOCKER_PASSWORD found
DEBUG Starting Docker IMPORT, includes env, runscript, and metadata.
VERBOSE2 Specified Docker ENTRYPOINT as %runscript.
DEBUG Headers found: Content-Type,Accept
VERBOSE Namespace:
VERBOSE Repo Name: YYYY
VERBOSE Repo Tag: ZZZZ
VERBOSE Version: None
DEBUG Http Error with code 401
ERROR Unrecognized authentication challenge, exiting.
+++ RETVAL=1
+++ '[' 1 -ne 0 ']'
+++ exit 1
Perhaps this is already fixed in another version of Singularity, but if so, which? My institution relies on the CentOS RPM version 2.6.0-dist. If this requires building singularity from source, I will need to know which version they should target.