-
Notifications
You must be signed in to change notification settings - Fork 27k
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
Using <Image /> component with-docker results in missing image-optimizer #32513
Comments
This ensures we trace the `image-optimizer` for the standalone output mode as previously this was always ignored under the assumption image optimizing would be handled at the CDN level in standalone mode. ## Bug - [x] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `yarn lint` Fixes: #32513
Hi, this has been updated in |
Can confirm, it's working with |
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. |
This ensures we trace the `image-optimizer` for the standalone output mode as previously this was always ignored under the assumption image optimizing would be handled at the CDN level in standalone mode. ## Bug - [x] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `yarn lint` Fixes: vercel#32513
What example does this report relate to?
with-docker
What version of Next.js are you using?
12.0.8
What version of Node.js are you using?
latest
What browser are you using?
Chrome
What operating system are you using?
macOS
How are you deploying your application?
Docker
Describe the Bug
When using the
<Image />
component in combination with the new standalone feature https://nextjs.org/docs/advanced-features/output-file-tracing results in theimage-optimizer.js
not being part of the copied node_modules and all request to the image produce a 500 error.Curl request to the image URL that is being requested by next.js in the frontend
result
docker build -t nextjs-docker .
.docker run -p 3000:3000 nextjs-docker
.docker exec -it $(docker ps -q) ash
cd node_modules/next/dist/server/
ls 0la
Output from Docker container file system after connecting with missing
image-optimizer.js
Expected Behavior
image-optimizer.js
is being part of node_modules when using standalone mode and 200 is returned with the image instead of 500To Reproduce
I created a minimal example here chrisdoc@3d8eb4d to reproduce that adds one
<Image />
tag with a reference to an external Image.The text was updated successfully, but these errors were encountered: