Open adgsenpai opened 6 months ago
facing the same issue on 14.2.1
Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!
nextjs is a really great framework but it's really tricky to use if it's not vercel..
Link to the code that reproduces this issue
https://github.com/adgsenpai/imageleakdemo
To Reproduce
WORKDIR /app
COPY package*.json ./ RUN npm install
COPY . .
RUN npm run build
EXPOSE 3000
CMD ["npm", "start"]
docker build -t nextjs-app .
docker run -p 3000:3000 nextjs-app
module.exports = { images: { domains: ['your-domain.com'], }, };
docker stats
Which area(s) are affected? (Select all that apply)
Image (next/image)
Which stage(s) are affected? (Select all that apply)
next build (local)
Additional context
Deployment Platform: Docker Reproducibility: The issue is consistently reproducible in the Docker environment. It does not occur when running the application locally outside of Docker. Browsers: The memory leak is observed regardless of the browser used to access the application, indicating it is not browser-specific. Environment: The issue has been specifically noted when running on Alpine Linux with the following setup: Platform: linux Arch: x64 Version: Alpine Linux