cdk deploy -failed

[chandra-pexa]

cdk failed with following error. Can someone help ?

6 218.9 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again

6 ERROR: process "/bin/sh -c yum update -y && yum install -y amazon-linux-extras && PYTHON=python2 amazon-linux-extras install epel && yum -y install clamav clamd p7zip && yum clean all && pip3 install --no-cache-dir cffi awslambdaric boto3 requests aws-lambda-powertools && ln -s /etc/freshclam.conf /tmp/freshclam.conf" did not complete successfully: exit code: 1

---

[2/4] RUN yum update -y && yum install -y amazon-linux-extras && PYTHON=python2 amazon-linux-extras install epel && yum -y install clamav clamd p7zip && yum clean all && pip3 install --no-cache-dir cffi awslambdaric boto3 requests aws-lambda-powertools && ln -s /etc/freshclam.conf /tmp/freshclam.conf: 218.9 218.9 5. Configure the failing repository to be skipped, if it is unavailable. 218.9 Note that yum will try to contact the repo. when it runs most commands, 218.9 so will have to try and fail each time (and thus. yum will be be much 218.9 slower). If it is a very temporary problem though, this is often a nice 218.9 compromise: 218.9 218.9 yum-config-manager --save --setopt=.skip_if_unavailable=true 218.9 218.9 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again

[chandra-pexa]

✨ Synthesis time: 4.1s

CdkTestStack: start: Building 7f18a11296f35510ee16538afec983ed6312e12afbf81b777089a9f8e34e2474:current_account-current_region CdkTestStack: success: Built 7f18a11296f35510ee16538afec983ed6312e12afbf81b777089a9f8e34e2474:current_account-current_region CdkTestStack: start: Publishing 7f18a11296f35510ee16538afec983ed6312e12afbf81b777089a9f8e34e2474:current_account-current_region CdkTestStack: start: Building 5194f926380567b6fdffc61629afdad2afc818614cb227df45e499c69db163a7:current_account-current_region CdkTestStack: success: Built 5194f926380567b6fdffc61629afdad2afc818614cb227df45e499c69db163a7:current_account-current_region CdkTestStack: start: Building 7d289f9862096a0365073560bf6f447a02ebc74681e6aa4baaaa3a61c8e53bac:current_account-current_region CdkTestStack: success: Built 7d289f9862096a0365073560bf6f447a02ebc74681e6aa4baaaa3a61c8e53bac:current_account-current_region CdkTestStack: start: Publishing 5194f926380567b6fdffc61629afdad2afc818614cb227df45e499c69db163a7:current_account-current_region CdkTestStack: start: Building 900e866a2f7ed9b5f68ec5c0f8d7486e23ac1d943f7531ead40771cd799ebafc:current_account-current_region CdkTestStack: success: Built 900e866a2f7ed9b5f68ec5c0f8d7486e23ac1d943f7531ead40771cd799ebafc:current_account-current_region CdkTestStack: start: Publishing 7d289f9862096a0365073560bf6f447a02ebc74681e6aa4baaaa3a61c8e53bac:current_account-current_region CdkTestStack: start: Building 170c35a7e22f1db8d1ddca89e432b257de298fb8d43e611a15b64d36b7e5c229:current_account-current_region CdkTestStack: start: Publishing 900e866a2f7ed9b5f68ec5c0f8d7486e23ac1d943f7531ead40771cd799ebafc:current_account-current_region CdkTestStack: success: Published 5194f926380567b6fdffc61629afdad2afc818614cb227df45e499c69db163a7:current_account-current_region CdkTestStack: success: Published 7f18a11296f35510ee16538afec983ed6312e12afbf81b777089a9f8e34e2474:current_account-current_region CdkTestStack: success: Published 7d289f9862096a0365073560bf6f447a02ebc74681e6aa4baaaa3a61c8e53bac:current_account-current_region CdkTestStack: success: Published 900e866a2f7ed9b5f68ec5c0f8d7486e23ac1d943f7531ead40771cd799ebafc:current_account-current_region

0 building with "desktop-linux" instance using docker driver

1 [internal] load .dockerignore

1 transferring context: 2B done

1 DONE 0.0s

2 [internal] load build definition from Dockerfile

2 transferring dockerfile: 768B done

2 DONE 0.0s

3 [internal] load metadata for public.ecr.aws/lambda/python:3.8

3 DONE 1.8s

4 [1/4] FROM public.ecr.aws/lambda/python:3.8@sha256:792f2bf43029d35f88de33a4d244db99e8d81319ce4e306d1ba257a0a9a16b30

4 CACHED

5 [internal] load build context

5 transferring context: 10.50kB done

5 DONE 0.0s

6 [2/4] RUN yum update -y && yum install -y amazon-linux-extras && PYTHON=python2 amazon-linux-extras install epel && yum -y install clamav clamd p7zip && yum clean all && pip3 install --no-cache-dir cffi awslambdaric boto3 requests aws-lambda-powertools && ln -s /etc/freshclam.conf /tmp/freshclam.conf

6 0.933 Loaded plugins: ovl

6 103.7 No packages marked for update

6 104.3 Loaded plugins: ovl

6 106.1 Resolving Dependencies

6 106.1 --> Running transaction check

6 106.1 ---> Package amazon-linux-extras.noarch 0:2.0.1-1.amzn2 will be installed

6 106.2 --> Finished Dependency Resolution

6 106.2

6 106.2 Dependencies Resolved

6 106.2

6 106.2 ================================================================================

6 106.2 Package Arch Version Repository Size

6 106.2 ================================================================================

6 106.2 Installing:

6 106.2 amazon-linux-extras noarch 2.0.1-1.amzn2 amzn2-core 38 k

6 106.2

6 106.2 Transaction Summary

6 106.2 ================================================================================

6 106.2 Install 1 Package

6 106.2

6 106.2 Total download size: 38 k

6 106.2 Installed size: 106 k

6 106.2 Downloading packages:

6 109.8 Running transaction check

6 109.8 Running transaction test

6 109.8 Transaction test succeeded

6 109.9 Running transaction

6 109.9 Installing : amazon-linux-extras-2.0.1-1.amzn2.noarch 1/1

6 110.0 Verifying : amazon-linux-extras-2.0.1-1.amzn2.noarch 1/1

6 110.0

6 110.0 Installed:

6 110.0 amazon-linux-extras.noarch 0:2.0.1-1.amzn2

6 110.0

6 110.0 Complete!

6 121.8 Loaded plugins: ovl

6 121.9 Cleaning repos: amzn2-core amzn2extra-epel

6 121.9 7 metadata files removed

6 121.9 1 sqlite file removed

6 121.9 0 metadata files removed

6 122.6 Loaded plugins: ovl

6 227.6 Resolving Dependencies

6 227.6 --> Running transaction check

6 227.6 ---> Package epel-release.noarch 0:7-11 will be installed

6 227.7 --> Finished Dependency Resolution

6 227.8

6 227.8 Dependencies Resolved

6 227.8

6 227.8 ================================================================================

6 227.8 Package Arch Version Repository Size

6 227.8 ================================================================================

6 227.8 Installing:

6 227.8 epel-release noarch 7-11 amzn2extra-epel 15 k

6 227.8

6 227.8 Transaction Summary

6 227.8 ================================================================================

6 227.8 Install 1 Package

6 227.8

6 227.8 Total download size: 15 k

6 227.8 Installed size: 24 k

6 227.8 Downloading packages:

6 228.4 Running transaction check

6 228.4 Running transaction test

6 228.4 Transaction test succeeded

6 228.4 Running transaction

6 228.4 Installing : epel-release-7-11.noarch 1/1

6 228.5 Verifying : epel-release-7-11.noarch 1/1

6 228.5

6 228.5 Installed:

6 228.5 epel-release.noarch 0:7-11

6 228.5

6 228.5 Complete!

6 236.0 Installing epel-release

6 236.0 2 httpd_modules available [ =1.0 =stable ]

6 236.0 3 memcached1.5 available \

6 236.0 [ =1.5.1 =1.5.16 =1.5.17 ]

6 236.0 9 R3.4 available [ =3.4.3 =stable ]

6 236.0 10 rust1 available \

6 236.0 [ =1.22.1 =1.26.0 =1.26.1 =1.27.2 =1.31.0 =1.38.0

6 236.0 =stable ]

6 236.0 18 libreoffice available \

6 236.0 [ =5.0.6.2_15 =5.3.6.1 =stable ]

6 236.0 19 gimp available [ =2.8.22 ]

6 236.0 20 †docker available \

6 236.0 [ =17.12.1 =18.03.1 =18.06.1 =18.09.9 =stable ]

6 236.0 21 mate-desktop1.x available \

6 236.0 [ =1.19.0 =1.20.0 =stable ]

6 236.0 22 GraphicsMagick1.3 available \

6 236.0 [ =1.3.29 =1.3.32 =1.3.34 =stable ]

6 236.0 23 †tomcat8.5 available \

6 236.0 [ =8.5.31 =8.5.32 =8.5.38 =8.5.40 =8.5.42 =8.5.50

6 236.0 =stable ]

6 236.0 24 epel=latest enabled [ =7.11 =stable ]

6 236.0 25 testing available [ =1.0 =stable ]

6 236.0 26 ecs available [ =stable ]

6 236.0 27 †corretto8 available \

6 236.0 [ =1.8.0_192 =1.8.0_202 =1.8.0_212 =1.8.0_222 =1.8.0_232

6 236.0 =1.8.0_242 =stable ]

6 236.0 32 lustre2.10 available \

6 236.0 [ =2.10.5 =2.10.8 =stable ]

6 236.0 33 †java-openjdk11 available [ =11 =stable ]

6 236.0 34 lynis available [ =stable ]

6 236.0 36 BCC available [ =0.x =stable ]

6 236.0 37 mono available [ =5.x =stable ]

6 236.0 38 nginx1 available [ =stable ]

6 236.0 40 mock available [ =stable ]

6 236.0 41 †postgresql11 available [ =11 =stable ]

6 236.0 43 livepatch available [ =stable ]

6 236.0 44 †python3.8 available [ =stable ]

6 236.0 45 haproxy2 available [ =stable ]

6 236.0 46 collectd available [ =stable ]

6 236.0 47 aws-nitro-enclaves-cli available [ =stable ]

6 236.0 48 R4 available [ =stable ]

6 236.0 49 kernel-5.4 available [ =stable ]

6 236.0 50 selinux-ng available [ =stable ]

6 236.0 51 †php8.0 available [ =stable ]

6 236.0 52 tomcat9 available [ =stable ]

6 236.0 53 unbound1.13 available [ =stable ]

6 236.0 54 †mariadb10.5 available [ =stable ]

6 236.0 55 kernel-5.10 available [ =stable ]

6 236.0 56 redis6 available [ =stable ]

6 236.0 57 †ruby3.0 available [ =stable ]

6 236.0 58 †postgresql12 available [ =stable ]

6 236.0 59 †postgresql13 available [ =stable ]

6 236.0 60 mock2 available [ =stable ]

6 236.0 61 dnsmasq2.85 available [ =stable ]

6 236.0 62 kernel-5.15 available [ =stable ]

6 236.0 63 †postgresql14 available [ =stable ]

6 236.0 64 firefox available [ =stable ]

6 236.0 65 lustre available [ =stable ]

6 236.0 66 †php8.1 available [ =stable ]

6 236.0 67 awscli1 available [ =stable ]

6 236.0 68 †php8.2 available [ =stable ]

6 236.0 69 dnsmasq available [ =stable ]

6 236.0 70 unbound1.17 available [ =stable ]

6 236.0 72 collectd-python3 available [ =stable ]

6 236.0 † Note on end-of-support. Use 'info' subcommand.

6 236.7 Loaded plugins: ovl

6 241.0

6 241.0

6 241.0 One of the configured repositories failed (Unknown),

6 241.0 and yum doesn't have enough cached data to continue. At this point the only

6 241.0 safe thing yum can do is fail. There are a few ways to work "fix" this:

6 241.0

6 241.0 1. Contact the upstream for the repository and get them to fix the problem.

6 241.0

6 241.0 2. Reconfigure the baseurl/etc. for the repository, to point to a working

6 241.0 upstream. This is most often useful if you are using a newer

6 241.0 distribution release than is supported by the repository (and the

6 241.0 packages for the previous distribution release still work).

6 241.0

6 241.0 3. Run the command with the repository temporarily disabled

6 241.0 yum --disablerepo= ...

6 241.0

6 241.0 4. Disable the repository permanently, so yum won't use it by default. Yum

6 241.0 will then just ignore the repository until you permanently enable it

6 241.0 again or use --enablerepo for temporary usage:

6 241.0

6 241.0 yum-config-manager --disable

6 241.0 or

6 241.0 subscription-manager repos --disable=

6 241.0

6 241.0 5. Configure the failing repository to be skipped, if it is unavailable.

6 241.0 Note that yum will try to contact the repo. when it runs most commands,

6 241.0 so will have to try and fail each time (and thus. yum will be be much

6 241.0 slower). If it is a very temporary problem though, this is often a nice

6 241.0 compromise:

6 241.0

6 241.0 yum-config-manager --save --setopt=.skip_if_unavailable=true

6 241.0

6 241.0 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again

6 ERROR: process "/bin/sh -c yum update -y && yum install -y amazon-linux-extras && PYTHON=python2 amazon-linux-extras install epel && yum -y install clamav clamd p7zip && yum clean all && pip3 install --no-cache-dir cffi awslambdaric boto3 requests aws-lambda-powertools && ln -s /etc/freshclam.conf /tmp/freshclam.conf" did not complete successfully: exit code: 1

---

[2/4] RUN yum update -y && yum install -y amazon-linux-extras && PYTHON=python2 amazon-linux-extras install epel && yum -y install clamav clamd p7zip && yum clean all && pip3 install --no-cache-dir cffi awslambdaric boto3 requests aws-lambda-powertools && ln -s /etc/freshclam.conf /tmp/freshclam.conf: 241.0 241.0 5. Configure the failing repository to be skipped, if it is unavailable. 241.0 Note that yum will try to contact the repo. when it runs most commands, 241.0 so will have to try and fail each time (and thus. yum will be be much 241.0 slower). If it is a very temporary problem though, this is often a nice 241.0 compromise: 241.0 241.0 yum-config-manager --save --setopt=.skip_if_unavailable=true 241.0 241.0 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again

Dockerfile:9

8 | ARG CACHE_DATE=1 9 | >>> RUN yum update -y \ 10 | >>> && yum install -y amazon-linux-extras \ 11 | >>> && PYTHON=python2 amazon-linux-extras install epel \ 12 | >>> && yum -y install clamav clamd p7zip \ 13 | >>> && yum clean all \ 14 | >>> && pip3 install --no-cache-dir cffi awslambdaric boto3 requests aws-lambda-powertools \ 15 | >>> && ln -s /etc/freshclam.conf /tmp/freshclam.conf 16 |

ERROR: failed to solve: process "/bin/sh -c yum update -y && yum install -y amazon-linux-extras && PYTHON=python2 amazon-linux-extras install epel && yum -y install clamav clamd p7zip && yum clean all && pip3 install --no-cache-dir cffi awslambdaric boto3 requests aws-lambda-powertools && ln -s /etc/freshclam.conf /tmp/freshclam.conf" did not complete successfully: exit code: 1 CdkTestStack: fail: docker build --build-arg 'CACHE_DATE=Wed Oct 04 2023' --tag cdkasset-170c35a7e22f1db8d1ddca89e432b257de298fb8d43e611a15b64d36b7e5c229 . exited with error code 1: #0 building with "desktop-linux" instance using docker driver

1 [internal] load .dockerignore

1 transferring context: 2B done

1 DONE 0.0s

2 [internal] load build definition from Dockerfile

2 transferring dockerfile: 768B done

2 DONE 0.0s

3 [internal] load metadata for public.ecr.aws/lambda/python:3.8

3 DONE 1.8s

4 [1/4] FROM public.ecr.aws/lambda/python:3.8@sha256:792f2bf43029d35f88de33a4d244db99e8d81319ce4e306d1ba257a0a9a16b30

4 CACHED

5 [internal] load build context

5 transferring context: 10.50kB done

5 DONE 0.0s

6 [2/4] RUN yum update -y && yum install -y amazon-linux-extras && PYTHON=python2 amazon-linux-extras install epel && yum -y install clamav clamd p7zip && yum clean all && pip3 install --no-cache-dir cffi awslambdaric boto3 requests aws-lambda-powertools && ln -s /etc/freshclam.conf /tmp/freshclam.conf

6 0.933 Loaded plugins: ovl

6 103.7 No packages marked for update

6 104.3 Loaded plugins: ovl

6 106.1 Resolving Dependencies

6 106.1 --> Running transaction check

6 106.1 ---> Package amazon-linux-extras.noarch 0:2.0.1-1.amzn2 will be installed

6 106.2 --> Finished Dependency Resolution

6 106.2

6 106.2 Dependencies Resolved

6 106.2

6 106.2 ================================================================================

6 106.2 Package Arch Version Repository Size

6 106.2 ================================================================================

6 106.2 Installing:

6 106.2 amazon-linux-extras noarch 2.0.1-1.amzn2 amzn2-core 38 k

6 106.2

6 106.2 Transaction Summary

6 106.2 ================================================================================

6 106.2 Install 1 Package

6 106.2

6 106.2 Total download size: 38 k

6 106.2 Installed size: 106 k

6 106.2 Downloading packages:

6 109.8 Running transaction check

6 109.8 Running transaction test

6 109.8 Transaction test succeeded

6 109.9 Running transaction

6 109.9 Installing : amazon-linux-extras-2.0.1-1.amzn2.noarch 1/1

6 110.0 Verifying : amazon-linux-extras-2.0.1-1.amzn2.noarch 1/1

6 110.0

6 110.0 Installed:

6 110.0 amazon-linux-extras.noarch 0:2.0.1-1.amzn2

6 110.0

6 110.0 Complete!

6 121.8 Loaded plugins: ovl

6 121.9 Cleaning repos: amzn2-core amzn2extra-epel

6 121.9 7 metadata files removed

6 121.9 1 sqlite file removed

6 121.9 0 metadata files removed

6 122.6 Loaded plugins: ovl

6 227.6 Resolving Dependencies

6 227.6 --> Running transaction check

6 227.6 ---> Package epel-release.noarch 0:7-11 will be installed

6 227.7 --> Finished Dependency Resolution

6 227.8

6 227.8 Dependencies Resolved

6 227.8

6 227.8 ================================================================================

6 227.8 Package Arch Version Repository Size

6 227.8 ================================================================================

6 227.8 Installing:

6 227.8 epel-release noarch 7-11 amzn2extra-epel 15 k

6 227.8

6 227.8 Transaction Summary

6 227.8 ================================================================================

6 227.8 Install 1 Package

6 227.8

6 227.8 Total download size: 15 k

6 227.8 Installed size: 24 k

6 227.8 Downloading packages:

6 228.4 Running transaction check

6 228.4 Running transaction test

6 228.4 Transaction test succeeded

6 228.4 Running transaction

6 228.4 Installing : epel-release-7-11.noarch 1/1

6 228.5 Verifying : epel-release-7-11.noarch 1/1

6 228.5

6 228.5 Installed:

6 228.5 epel-release.noarch 0:7-11

6 228.5

6 228.5 Complete!

6 236.0 Installing epel-release

6 236.0 2 httpd_modules available [ =1.0 =stable ]

6 236.0 3 memcached1.5 available \

6 236.0 [ =1.5.1 =1.5.16 =1.5.17 ]

6 236.0 9 R3.4 available [ =3.4.3 =stable ]

6 236.0 10 rust1 available \

6 236.0 [ =1.22.1 =1.26.0 =1.26.1 =1.27.2 =1.31.0 =1.38.0

6 236.0 =stable ]

6 236.0 18 libreoffice available \

6 236.0 [ =5.0.6.2_15 =5.3.6.1 =stable ]

6 236.0 19 gimp available [ =2.8.22 ]

6 236.0 20 †docker available \

6 236.0 [ =17.12.1 =18.03.1 =18.06.1 =18.09.9 =stable ]

6 236.0 21 mate-desktop1.x available \

6 236.0 [ =1.19.0 =1.20.0 =stable ]

6 236.0 22 GraphicsMagick1.3 available \

6 236.0 [ =1.3.29 =1.3.32 =1.3.34 =stable ]

6 236.0 23 †tomcat8.5 available \

6 236.0 [ =8.5.31 =8.5.32 =8.5.38 =8.5.40 =8.5.42 =8.5.50

6 236.0 =stable ]

6 236.0 24 epel=latest enabled [ =7.11 =stable ]

6 236.0 25 testing available [ =1.0 =stable ]

6 236.0 26 ecs available [ =stable ]

6 236.0 27 †corretto8 available \

6 236.0 [ =1.8.0_192 =1.8.0_202 =1.8.0_212 =1.8.0_222 =1.8.0_232

6 236.0 =1.8.0_242 =stable ]

6 236.0 32 lustre2.10 available \

6 236.0 [ =2.10.5 =2.10.8 =stable ]

6 236.0 33 †java-openjdk11 available [ =11 =stable ]

6 236.0 34 lynis available [ =stable ]

6 236.0 36 BCC available [ =0.x =stable ]

6 236.0 37 mono available [ =5.x =stable ]

6 236.0 38 nginx1 available [ =stable ]

6 236.0 40 mock available [ =stable ]

6 236.0 41 †postgresql11 available [ =11 =stable ]

6 236.0 43 livepatch available [ =stable ]

6 236.0 44 †python3.8 available [ =stable ]

6 236.0 45 haproxy2 available [ =stable ]

6 236.0 46 collectd available [ =stable ]

6 236.0 47 aws-nitro-enclaves-cli available [ =stable ]

6 236.0 48 R4 available [ =stable ]

6 236.0 49 kernel-5.4 available [ =stable ]

6 236.0 50 selinux-ng available [ =stable ]

6 236.0 51 †php8.0 available [ =stable ]

6 236.0 52 tomcat9 available [ =stable ]

6 236.0 53 unbound1.13 available [ =stable ]

6 236.0 54 †mariadb10.5 available [ =stable ]

6 236.0 55 kernel-5.10 available [ =stable ]

6 236.0 56 redis6 available [ =stable ]

6 236.0 57 †ruby3.0 available [ =stable ]

6 236.0 58 †postgresql12 available [ =stable ]

6 236.0 59 †postgresql13 available [ =stable ]

6 236.0 60 mock2 available [ =stable ]

6 236.0 61 dnsmasq2.85 available [ =stable ]

6 236.0 62 kernel-5.15 available [ =stable ]

6 236.0 63 †postgresql14 available [ =stable ]

6 236.0 64 firefox available [ =stable ]

6 236.0 65 lustre available [ =stable ]

6 236.0 66 †php8.1 available [ =stable ]

6 236.0 67 awscli1 available [ =stable ]

6 236.0 68 †php8.2 available [ =stable ]

6 236.0 69 dnsmasq available [ =stable ]

6 236.0 70 unbound1.17 available [ =stable ]

6 236.0 72 collectd-python3 available [ =stable ]

6 236.0 † Note on end-of-support. Use 'info' subcommand.

6 236.7 Loaded plugins: ovl

6 241.0

6 241.0

6 241.0 One of the configured repositories failed (Unknown),

6 241.0 and yum doesn't have enough cached data to continue. At this point the only

6 241.0 safe thing yum can do is fail. There are a few ways to work "fix" this:

6 241.0

6 241.0 1. Contact the upstream for the repository and get them to fix the problem.

6 241.0

6 241.0 2. Reconfigure the baseurl/etc. for the repository, to point to a working

6 241.0 upstream. This is most often useful if you are using a newer

6 241.0 distribution release than is supported by the repository (and the

6 241.0 packages for the previous distribution release still work).

6 241.0

6 241.0 3. Run the command with the repository temporarily disabled

6 241.0 yum --disablerepo= ...

6 241.0

6 241.0 4. Disable the repository permanently, so yum won't use it by default. Yum

6 241.0 will then just ignore the repository until you permanently enable it

6 241.0 again or use --enablerepo for temporary usage:

6 241.0

6 241.0 yum-config-manager --disable

6 241.0 or

6 241.0 subscription-manager repos --disable=

6 241.0

6 241.0 5. Configure the failing repository to be skipped, if it is unavailable.

6 241.0 Note that yum will try to contact the repo. when it runs most commands,

6 241.0 so will have to try and fail each time (and thus. yum will be be much

6 241.0 slower). If it is a very temporary problem though, this is often a nice

6 241.0 compromise:

6 241.0

6 241.0 yum-config-manager --save --setopt=.skip_if_unavailable=true

6 241.0

6 241.0 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again

6 ERROR: process "/bin/sh -c yum update -y && yum install -y amazon-linux-extras && PYTHON=python2 amazon-linux-extras install epel && yum -y install clamav clamd p7zip && yum clean all && pip3 install --no-cache-dir cffi awslambdaric boto3 requests aws-lambda-powertools && ln -s /etc/freshclam.conf /tmp/freshclam.conf" did not complete successfully: exit code: 1

---

[2/4] RUN yum update -y && yum install -y amazon-linux-extras && PYTHON=python2 amazon-linux-extras install epel && yum -y install clamav clamd p7zip && yum clean all && pip3 install --no-cache-dir cffi awslambdaric boto3 requests aws-lambda-powertools && ln -s /etc/freshclam.conf /tmp/freshclam.conf: 241.0 241.0 5. Configure the failing repository to be skipped, if it is unavailable. 241.0 Note that yum will try to contact the repo. when it runs most commands, 241.0 so will have to try and fail each time (and thus. yum will be be much 241.0 slower). If it is a very temporary problem though, this is often a nice 241.0 compromise: 241.0 241.0 yum-config-manager --save --setopt=.skip_if_unavailable=true 241.0 241.0 Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again

Dockerfile:9

8 | ARG CACHE_DATE=1 9 | >>> RUN yum update -y \ 10 | >>> && yum install -y amazon-linux-extras \ 11 | >>> && PYTHON=python2 amazon-linux-extras install epel \ 12 | >>> && yum -y install clamav clamd p7zip \ 13 | >>> && yum clean all \ 14 | >>> && pip3 install --no-cache-dir cffi awslambdaric boto3 requests aws-lambda-powertools \ 15 | >>> && ln -s /etc/freshclam.conf /tmp/freshclam.conf 16 |

ERROR: failed to solve: process "/bin/sh -c yum update -y && yum install -y amazon-linux-extras && PYTHON=python2 amazon-linux-extras install epel && yum -y install clamav clamd p7zip && yum clean all && pip3 install --no-cache-dir cffi awslambdaric boto3 requests aws-lambda-powertools && ln -s /etc/freshclam.conf /tmp/freshclam.conf" did not complete successfully: exit code: 1

❌ Deployment failed: Error: Failed to build asset 170c35a7e22f1db8d1ddca89e432b257de298fb8d43e611a15b64d36b7e5c229:current_account-current_region at Deployments.buildSingleAsset (/opt/homebrew/lib/node_modules/aws-cdk/lib/index.js:470:11115) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Object.buildAsset (/opt/homebrew/lib/node_modules/aws-cdk/lib/index.js:470:177544) at async /opt/homebrew/lib/node_modules/aws-cdk/lib/index.js:470:163212

Failed to build asset 170c35a7e22f1db8d1ddca89e432b257de298fb8d43e611a15b64d36b7e5c229:current_account-current_region

[dontirun]

I'm unable to reproduce this problem.

@chandra-pexa Can you test if this issue persists after clearing your docker image cache and attempting another cdk deploy?

[chandra-pexa]

@dontirun i did clear the docker cache and tried again. I end with same error.

[dontirun]

Hmm, are you behind any sort of network proxy?

[chandra-pexa]

yes, this is on my work laptop.

[dontirun]

Is the epel repo blocked on your work network?

[dontirun]

@chandra-pexa Do you see the same issue if you use version 2.6.0 or later?

[andresfelipe9619]

This happened to me after cleaning out my disk space and removing some docker images, containers, volumes and builds... so i think this broke somehow the cdk.

I solved this by removing the cdk.out folder, then bootstrapping the project with cdk bootstrap, the deploy worked fine