https://cdn.amazonlinux.com/2/core/2.0/aarch64/95051b33cb06275a2be90f45ee8fbd12a95dc2afe7ba94bff90e197f4d6a9403/repodata/repomd.xml?instance_id=URLError&region=unknown: [Errno 14] curl#60 - "SSL certificate problem: unable to get local issuer certificate"

[yeswanth-bf]

$ ./mwaa-local-env build-image
[+] Building 4.4s (14/25) docker:desktop-linux
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 3.54kB 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/amazonlinux:2 0.7s
=> [ 1/21] FROM docker.io/library/amazonlinux:2@sha256:4f39d87731b57d3be630f9877ab25c4f4cfa8adc3039592c8c00a14235cb2a2b 0.0s
=> [internal] load build context 0.0s
=> => transferring context: 573B 0.0s
=> CACHED [ 2/21] COPY script/bootstrap.sh /bootstrap.sh 0.0s
=> [ 3/21] COPY script/systemlibs.sh /systemlibs.sh 0.0s
=> [ 4/21] COPY script/generate_key.sh /generate_key.sh 0.0s
=> [ 5/21] COPY script/run-startup.sh /run-startup.sh 0.0s
=> [ 6/21] COPY script/shell-launch-script.sh /shell-launch-script.sh 0.0s
=> [ 7/21] COPY script/verification.sh /verification.sh 0.0s
=> [ 8/21] COPY config/constraints.txt /constraints.txt 0.0s
=> [ 9/21] COPY config/mwaa-base-providers-requirements.txt /mwaa-base-providers-requirements.txt 0.0s
=> ERROR [10/21] RUN chmod u+x /systemlibs.sh && /systemlibs.sh 3.6s

[10/21] RUN chmod u+x /systemlibs.sh && /systemlibs.sh:
0.163 Loaded plugins: ovl, priorities
3.563 https://cdn.amazonlinux.com/2/core/2.0/aarch64/95051b33cb06275a2be90f45ee8fbd12a95dc2afe7ba94bff90e197f4d6a9403/repodata/repomd.xml?instance_id=URLError&region=unknown: [Errno 14] curl#60 - "SSL certificate problem: unable to get local issuer certificate"
3.563 Trying other mirror.
3.564
3.564
3.564 One of the configured repositories failed (Amazon Linux 2 core repository),
3.564 and yum doesn't have enough cached data to continue. At this point the only
3.564 safe thing yum can do is fail. There are a few ways to work "fix" this:
3.564
3.564 1. Contact the upstream for the repository and get them to fix the problem.
3.564
3.564 2. Reconfigure the baseurl/etc. for the repository, to point to a working
3.564 upstream. This is most often useful if you are using a newer
3.564 distribution release than is supported by the repository (and the
3.564 packages for the previous distribution release still work).
3.564
3.564 3. Run the command with the repository temporarily disabled
3.564 yum --disablerepo=amzn2-core ...
3.564
3.564 4. Disable the repository permanently, so yum won't use it by default. Yum
3.564 will then just ignore the repository until you permanently enable it
3.564 again or use --enablerepo for temporary usage:
3.564
3.564 yum-config-manager --disable amzn2-core
3.564 or
3.564 subscription-manager repos --disable=amzn2-core
3.564
3.564 5. Configure the failing repository to be skipped, if it is unavailable.
3.564 Note that yum will try to contact the repo. when it runs most commands,
3.564 so will have to try and fail each time (and thus. yum will be be much
3.564 slower). If it is a very temporary problem though, this is often a nice
3.564 compromise:
3.564
3.564 yum-config-manager --save --setopt=amzn2-core.skip_if_unavailable=true
3.564
3.564 failure: repodata/repomd.xml from amzn2-core: [Errno 256] No more mirrors to try.
3.564 https://cdn.amazonlinux.com/2/core/2.0/aarch64/95051b33cb06275a2be90f45ee8fbd12a95dc2afe7ba94bff90e197f4d6a9403/repodata/repomd.xml?instance_id=URLError&region=unknown: [Errno 14] curl#60 - "SSL certificate problem: unable to get local issuer certificate"

---

Dockerfile:34

32 | COPY config/mwaa-base-providers-requirements.txt /mwaa-base-providers-requirements.txt
33 |
34 | >>> RUN chmod u+x /systemlibs.sh && /systemlibs.sh
35 | RUN chmod u+x /bootstrap.sh && /bootstrap.sh
36 | RUN chmod u+x /generate_key.sh && /generate_key.sh

ERROR: failed to solve: process "/bin/sh -c chmod u+x /systemlibs.sh && /systemlibs.sh" did not complete successfully: exit code: 1

[yeswanth-bf]

I am running local-mwaa on Mac Apple M1 Pro Chip