Closed loesak closed 9 months ago
I am unsure if this is the correct repository for this issue or if it should exist over here: https://github.com/aws/aws-lambda-base-images/issues
Issue has been resolved and discussion occurred in https://github.com/aws/aws-lambda-base-images/issues
Description:
We've been using the image
public.ecr.aws/lambda/python:3.11-x86_64
for building our Python based Lambda ZIP artifacts for use by the AWS Lambda Python 3.11 runtime. We are not using the image for building other Docker images for running a Docker based AWS Lambda runtimes (please let me know if this is not a supported use case for this Docker image). However, I believe this is an issue for also building subsequent Docker images. It seems recently the base image was updated and the deprecatedyum
command is no longer present and thednf
command should be used instead to install OS packages. However, when running thednf
command, results in an error.This is preventing us from installing needed dependencies we need for performing our build but I assume it would also be needed to install any OS packages for any Docker image based off this image.
Steps to reproduce:
Start a container based on this image:
or to pin to the image where this issue was discovered:
then try to run the
dnf
command:Observed result:
Expected result:
Expected
dnf
command to execute successfully w/o errorAdditional environment details (Ex: Windows, Mac, Amazon Linux etc)
None