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

Open
1 task done
w4-hanggi opened this issue Mar 11, 2022 · 1 comment · May be fixed by #35535
Open
1 task done

standalone not works with pnpm in docker #35235

w4-hanggi opened this issue Mar 11, 2022 · 1 comment · May be fixed by #35535
Labels
area: examples good first issue

Comments

@w4-hanggi
Copy link

@w4-hanggi w4-hanggi commented Mar 11, 2022

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 template: bug label Mar 11, 2022
@balazsorban44 balazsorban44 added area: examples good first issue and removed template: bug labels Mar 11, 2022
@siva-kannan3
Copy link

@siva-kannan3 siva-kannan3 commented Mar 14, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: examples good first issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants