We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This solution needs ECR image for private workflow to run successfully. Otherwise private workflow run fails with below mentioned error:
{ “runStatus”: “RUNNING”, “logMessage”: “ECR_PERMISSION_ERROR”, “message”: “Unable to access image URI: 0000000000.dkr.ecr.us-east-1.amazonaws.com/quay/biocontainers/ensembl-vep:106.1--pl5321h4a94de4_0. Ensure the ECR private repository exists and has granted access for the omics service principle to access the repository.” }
Solution: Run amazon-ecr-helper-for-aws-healthomics helper utility with following container_image_manifest.json file:
{ "manifest": [ "quay.io/biocontainers/ensembl-vep:106.1--pl5321h4a94de4_0" ] }
Execute the following to pull this list of container images into your ECR private registry:
aws stepfunctions start-execution \ --state-machine-arn arn:aws:states:<aws-region>:<aws-account-id>:stateMachine:omx-container-puller \ --input file://container_image_manifest.json
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This solution needs ECR image for private workflow to run successfully. Otherwise private workflow run fails with below mentioned error:
Solution:
Run amazon-ecr-helper-for-aws-healthomics helper utility with following container_image_manifest.json file:
{ "manifest": [ "quay.io/biocontainers/ensembl-vep:106.1--pl5321h4a94de4_0" ] }
Execute the following to pull this list of container images into your ECR private registry:
aws stepfunctions start-execution \ --state-machine-arn arn:aws:states:<aws-region>:<aws-account-id>:stateMachine:omx-container-puller \ --input file://container_image_manifest.json
The text was updated successfully, but these errors were encountered: