-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Next js container crashes and gets restarted when it renders <Image /> #22644
Comments
Can you try using |
@timneutkens Sure! But why would you suggest that? Is it going to log anything that could be useful? Sorry I'm not really sure what canary updates are. |
Canary is our beta channel. It holds any changes made before a stable release is done. In this case we've replaced |
@timneutkens God bless you! It solved my problem. Can I ask you to answer this stackoverflow question so that others could use it? Let me know if it's better to close the stackoverflow question. |
Great, thanks for verifying 👍 We're planning to release a new stable version very soon. |
@timneutkens we upgraded to 10.2.0 because of a memory leak issue with the Image tag, do you know if this is related to the error in this thread? Is 10.2.0 expected to solve this? |
This issue can be closed as the initial post was solved and published on stable. @fe-rod make sure you upgrade to the latest version of Next.js as it has a bunch of memory improvements. |
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
What version of Next.js are you using?
10.0.7
What version of Node.js are you using?
12.16.0
What browser are you using?
firefox, ...
What operating system are you using?
Ubuntu
How are you deploying your application?
next start
Describe the Bug
when a page renders "next/image", nextjs container gets restarted without any errors. "kubectl logs" and "kubectl describe" shows nothing. The kubernetes pod's status goes from "RUNNING" to "COMPLETED" and nextjs container gets restarted.
Expected Behavior
I expect "next/image" to optimize the image and work properly, or at least show me errors about my problem. But it
To Reproduce
I want to use nextjs image optimization in my nextjs microservice which is deployed on a kubernetes cluster. But the nextjs container gets crashed and restarted whenever it has to render a "next/image" component. Here is the detailed steps to reproduce the scenario:
Steps to reproduce:
media
on it on copy some images intomedia
.backend
. (So that in other pods, images could be requested by urls like "http://backend
/media/image-1.jpg")backend
to image domains in next.config.js:next/image
:next/image
.RUNNING
toCOMPLETED
without any errors or logs. And the nextjs container gets restarted.My question is:
How to use nextjs image optimization when images are served from another kubernetes microservice?
The text was updated successfully, but these errors were encountered: