-
-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
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
Enable new image for Nouveau to be published in CI to Elastic Container Repository (ECR) #9685
Comments
@m5r reported running the CI job now, this error is returned:
@henokgetachew tried to add some perms in ECR: {
"repository": {
"repositoryArn": "arn:aws:ecr:eu-west-2:720541322708:repository/medic/cht-couchdb-nouveau",
"registryId": "720541322708",
"repositoryName": "medic/cht-couchdb-nouveau",
"repositoryUri": "720541322708.dkr.ecr.eu-west-2.amazonaws.com/medic/cht-couchdb-nouveau",
"createdAt": "2024-12-03T13:05:44.979000+03:00",
"imageTagMutability": "MUTABLE",
"imageScanningConfiguration": {
"scanOnPush": false
},
"encryptionConfiguration": {
"encryptionType": "AES256"
}
}
} |
The issue here was very simple that it was difficult not to overlook. The repo i created was a private repo. Not a public one. |
@m5r can you now test? |
@henokgetachew just gave it two more tries to be certain and it's still failing 😟 https://github.com/medic/cht-core/actions/runs/12273653842/job/34244889443?pr=9541#step:13:875 |
Ah, now I see the issue! The way the builds work is that branch builds are pushed to the private repo whereas master builds are pushed to the public repo. Private Registry Push:
Public Registry Push:
The error we were seeing earlier was because the code is trying to push to the private registry but using the repository that was set up in the public registry. Not sure where in the build that's configured (cc: @dianabarsan ) |
Describe the issue
A new service is being added to CHT Core, Nouveau, and it needs a new image published via CI
Describe the improvement you'd like
Do any ECR and related work to allow the image to be published
The text was updated successfully, but these errors were encountered: