aws / aws/aws-lambda-base-images
python 3.10
- Dominant language
- No language data
- Stars
- 777
- Forks
- 118
- PR merge metrics
- No merged PRs in 30d
Description
Dockerfile
FROM public.ecr.aws/lambda/python:3.10
RUN yum install -y -q sudo unzip
When I run in terminal
docker build -t example .
#0 0.562 Loaded plugins: ovl
#0 38.82
#0 38.82
#0 38.82 One of the configured repositories failed (Unknown),
#0 38.82 and yum doesn't have enough cached data to continue. At this point the only
#0 38.82 safe thing yum can do is fail. There are a few ways to work "fix" this:
#0 38.82
#0 38.82 1. Contact the upstream for the repository and get them to fix the problem.
#0 38.82
#0 38.82 2. Reconfigure the baseurl/etc. for the repository, to point to a working
#0 38.82 upstream. This is most often useful if you are using a newer
#0 38.82 distribution release than is supported by the repository (and the
#0 38.82 packages for the previous distribution release still work).
#0 38.82
#0 38.82 3. Run the command with the repository temporarily disabled
#0 38.82 yum --disablerepo= ...
#0 38.82
#0 38.82 4. Disable the repository permanently, so yum won't use it by default. Yum
#0 38.82 will then just ignore the repository until you permanently enable it
#0 38.82 again or use --enablerepo for temporary usage:
#0 38.82
#0 38.82 yum-config-manager --disable
#0 38.82 or
#0 38.82 subscription-manager repos --disable=
#0 38.82
#0 38.82 5. Configure the failing repository to be skipped, if it is unavailable.
#0 38.82 Note that yum will try to contact the repo. when it runs most commands,
#0 38.82 so will have to try and fail each time (and thus. yum will be be much
#0 38.82 slower). If it is a very temporary problem though, this is often a nice
#0 38.82 compromise:
#0 38.82
#0 38.82 yum-config-manager --save --setopt=.skip_if_unavailable=true
#0 38.82
#0 38.82 **Cannot find a valid baseurl for repo: amzn2-core/2/x86_64**
#0 38.82 **Could not retrieve mirrorlist http://amazonlinux.default.amazonaws.com/2/core/latest/x86_64/mirror.list error was
#0 38.82 12: Timeout on http://amazonlinux.default.amazonaws.com/2/core/latest/x86_64/mirror.list: (28, 'Resolving timed out after 5000 milliseconds')**
Can someone help me to solve this error?
Contributor guide
Assessment
This issue has not been assessed yet.