CDK deployment failing: repository does not exist in the registry

[Maksym94]

Hello all,

I've faced an error in Workshop on Step 6: cdk deploy
CdkStackALBEksBg stack failed with the following logs:

CdkStackALBEksBg: deploying...
[0%] start: Publishing 26ac61b4195cccf80ff73f332788ad7ffaab36d81ce570340a583a8364901665:current
[10%] success: Published 26ac61b4195cccf80ff73f332788ad7ffaab36d81ce570340a583a8364901665:current
[10%] start: Publishing 3144c5280df58e5cdbad2fdc0464c2dc114b48bdc883d5964c0f7cf329e191fa:current
[20%] success: Published 3144c5280df58e5cdbad2fdc0464c2dc114b48bdc883d5964c0f7cf329e191fa:current
[20%] start: Publishing c691172cdeefa2c91b5a2907f9d81118e47597634943344795f1a844192dd49c:current
[30%] success: Published c691172cdeefa2c91b5a2907f9d81118e47597634943344795f1a844192dd49c:current
[30%] start: Publishing 4129bbca38164ecb28fee8e5b674f0d05e5957b4b8ed97d9c950527b5cc4ce10:current
[40%] success: Published 4129bbca38164ecb28fee8e5b674f0d05e5957b4b8ed97d9c950527b5cc4ce10:current
[40%] start: Publishing e9882ab123687399f934da0d45effe675ecc8ce13b40cb946f3e1d6141fe8d68:current
[50%] success: Published e9882ab123687399f934da0d45effe675ecc8ce13b40cb946f3e1d6141fe8d68:current
[50%] start: Publishing ea17febe6d04c66048f3e8e060c71685c0cb53122abceff44842d27bc0d4a03e:current
[60%] success: Published ea17febe6d04c66048f3e8e060c71685c0cb53122abceff44842d27bc0d4a03e:current
[60%] start: Publishing 540c42bf93221d226e9892dca8f369ca800db0f340fb22015b9723dd093760e1:current
[70%] success: Published 540c42bf93221d226e9892dca8f369ca800db0f340fb22015b9723dd093760e1:current
[70%] start: Publishing 81cf0917f6b2b41f4037af7e72c7c75993aa9f419a182bc27d6e30e2d55bcf94:current
[80%] success: Published 81cf0917f6b2b41f4037af7e72c7c75993aa9f419a182bc27d6e30e2d55bcf94:current
[80%] start: Publishing 587eec5f7189189557b02f86a2f8dd746bb63d0b11a488ee97d629d2eeb72336:current
[90%] success: Published 587eec5f7189189557b02f86a2f8dd746bb63d0b11a488ee97d629d2eeb72336:current
[90%] start: Publishing f49a00e629119a89acb65cce47bbf091d7dab3ec26220bca4923d04c4d3f4cd2:current
Sending build context to Docker daemon   5.12kB
Step 1/10 : FROM public.ecr.aws/p8v8e7e5/myartifacts:alpine-jan2021
repository public.ecr.aws/p8v8e7e5/myartifacts not found: name unknown: The repository with name 'myartifacts' does not exist in the registry with id 'p8v8e7e5'
[100%] fail: docker build --tag cdkasset-f49a00e629119a89acb65cce47bbf091d7dab3ec26220bca4923d04c4d3f4cd2 . exited with error code 1: repository public.ecr.aws/p8v8e7e5/myartifacts not found: name unknown: The repository with name 'myartifacts' does not exist in the registry with id 'p8v8e7e5'

Environment:

cdk version - 1.134.0 (build dd5e12d)
aws version - aws-cli/1.19.112 Python/2.7.18 Linux/4.14.301-224.520.amzn2.x86_64 botocore/1.20.112
npm version - 6.14.17

Could you suggest if I missed something or public repository has been deleted recently?
Thank you.

[danny-kirby]

Just adding to this, the issue is still appearing as well for me as of this post 17 Feb 2023. I did follow the pre-setup on the README here in addition to the workshop steps, so it seems like something changed.

Seems the this public registry doesn't exist anymore perhaps? source

Edit:
Made an update to pull from public.ecr.aws/docker/library/alpine:3.17.2 instead on the Dockerfile and that resolve pulling.
There's also another issue when k8s attempts to pull down the flask image dockerfile . You'll need to update this one as well.

[alekasw]

@danny-kirby Thank you for providing a fix.