Skip to content
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

standalone not works with pnpm in docker #35235

Closed
1 task done
w4-hanggi opened this issue Mar 11, 2022 · 2 comments · Fixed by #35535
Closed
1 task done

standalone not works with pnpm in docker #35235

w4-hanggi opened this issue Mar 11, 2022 · 2 comments · Fixed by #35535
Labels
examples Issue/PR related to examples good first issue Easy to fix issues, good for newcomers

Comments

@w4-hanggi
Copy link

Verify canary release

  • I verified that the issue exists in Next.js canary release

Provide environment information

Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 21.3.0: Wed Jan  5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64
Binaries:
  Node: 16.14.0
  npm: 8.3.1
  Yarn: 1.22.17
  pnpm: 6.32.3
Relevant packages:
  next: 12.1.0
  react: 17.0.2
  react-dom: 17.0.2

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

The generated standalone with pnpm are symbolink.
In step docker build, it will not contain the pnpm node_modules

Expected Behavior

Use non symbol link in standalone output.

To Reproduce

https://github.com/vercel/next.js/tree/canary/examples/with-docker

just execute the example with pnpm

@w4-hanggi w4-hanggi added the bug Issue was opened via the bug report template. label Mar 11, 2022
@balazsorban44 balazsorban44 added examples Issue/PR related to examples good first issue Easy to fix issues, good for newcomers and removed bug Issue was opened via the bug report template. labels Mar 11, 2022
@siva-kannan3
Copy link

siva-kannan3 commented Mar 14, 2022

I'd like to work on it. Can you explain it further?

@github-actions
Copy link
Contributor

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
examples Issue/PR related to examples good first issue Easy to fix issues, good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants