yum seems to have vanished - Amazon Linux 2023?

[slodge]

Just working on #25 and I'm hitting:

Step 3/20 : RUN yum -y install wget git tar
 ---> Running in b5fda99a9abf
/bin/sh: line 1: yum: command not found
Error: The command '/bin/sh -c yum -y install wget git tar' returned a non-zero code: 127

It seems like this might be a change with AWS: https://www.reddit.com/r/aws/comments/17uahqv/why_yum_command_stopped_working_on_latest/

[slodge]

Am not entirely sure what I'm doing here - but am experimenting with switching yum to dnf

Am now hitting problems with epel-release - looks like that's not supported on AL 2023 - https://repost.aws/knowledge-center/ec2-enable-epel (but I'm not sure what epel-release is for)

Also looking at https://aws.amazon.com/blogs/compute/introducing-the-amazon-linux-2023-runtime-for-aws-lambda/ and at amazon-linux-extras ... but really learning/reading as I go here (and not got much time on this until later in the week 👍

[jameswcraig]

Hi @slodge , I also just ran into this issue. Were you able to make any changes to https://github.com/discindo/r2lambda/blob/main/inst/lambdr_dockerfile.txt to get things working?

[slodge]

Sorry. I ran into other priorities so haven't progressed this (my r job is already running in Azure and moving it to Aws is an experiment rather than an essential task). The change from yum to dnf on its own seemed trivial - but I think there are other amazonlinux2023 issues lurking here too. I was going to look at changing the FROM container image back to Amazon Linux 2 (rather than latest), but I haven't spent more than a few minutes on this yet.

…

On Sat, 9 Dec 2023, 16:03 James Craig, ***@***.***> wrote: Hi @slodge <https://github.com/slodge> , I also just ran into this issue. Were you able to make any changes to https://github.com/discindo/r2lambda/blob/main/inst/lambdr_dockerfile.txt to get things working? — Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAECJHWHVL4LYZ6EBNL5ERTYISDURAVCNFSM6AAAAAA72WTNLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBYGQ2DQOBRGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jameswcraig]

Thanks @slodge - I was able to get the example running by changing to FROM public.ecr.aws/lambda/python:3.8

[novica]

Amazon linux for lambda uses microdnf package manager as per AWS docs. Have you tried this?

[slodge]

I did try just replacing yum with dnf - but immediately hit epel issues.

I haven't invested time in this yet and probably won't. I am intending to work on #27 but will leave this to people more experienced in Linux, especially if I can use the python:3.8 container to continue for now👍