actions / runner-images

GitHub Actions runner images
MIT License
9.12k stars 2.82k forks source link

Fail to build nextjs app since 20240407.1.0 #9700

Closed tyx closed 2 weeks ago

tyx commented 2 weeks ago

Description

Hi,

I just don't get what is going on since a week and the new runner image 20240407.1.0 with ubuntu-22.04 but I am no longer able to build my nextjs app...

Error looks around the locate detection : image

Please note we add no error with runner image 20240324.2.0 and the same build that pass with this image, no longer build with the new image. No change on our side. (I rerun an old build to be sure the problem was the runner image)

Platforms affected

Runner images affected

Image version and build link

20240407.1.0

Is it regression?

20240324.2.0

Expected behavior

I expect my nextjs app build

Actual behavior

image

Repro steps

I will try to isolate the issue but I have no idea for now what is going on and how an update of runner image could break a nextjs build.

MaksimZhukov commented 2 weeks ago

Hello @tyx! Please provide us with repro steps for further investigation. It would be great if you could provide us with a link to the public repository where the issue occurs.

tyx commented 2 weeks ago

Unfortunately it is a private repository. I am working on a repro step right now

tyx commented 2 weeks ago

After hours isolating the problem I was able to confirm that the problem was linked to the tricks in the nextjs doc to redirect our default locale to /en.

So we end up with a default locale in our getStaticProps, which up until now hasn't caused any problems because the result of the locale negotiation is that we end up with the default locale.

It seems that the problem is linked to formatjs and i18n and the way of determining whether a locale is valid or not.

I imagine it must be based on a system call and that's why we got the error on the new image and on a new docker image.

Sorry for the inconvenience!