Sharp required for standalone mode

[vasanthi-d]

I am using next.js standalone mode and I am following with-docker example quoted on Next.js for containerizing the app.
When run and access the app, I get below error

Error: 'sharp' is required to be installed in standalone mode for the image optimization to function correctly

I have installed 'sharp' and it is part of my node_modules. What am I missing?

[martinIvovIv]

I am having a similar issue.
From the official documentation:
If sharp is already installed but can't be resolved, set the NEXT_SHARP_PATH environment variable such as export NEXT_SHARP_PATH=/tmp/node_modules/sharp. Then, build your project with next build. Finally, restart the server with either next start for production mode or node server.js for standalone mode.
https://nextjs.org/docs/messages/sharp-missing-in-production

Try this approach, if it doesn't work, see below.

But I am not sure about setting the env variable.
I found some relevant StackOverflow threads and if that doesn't work try adding it in docker as:
ENV NEXT_SHARP_PATH=/tmp/node_modules/sharp

[asrudii]

I solved with added several command in dockerfile :

1. add "RUN npm i sharp" in deps section
2. add "COPY --from=deps /root/.npm /root/.npm" in builder section before RUN npm run build
3. add "ENV NEXT_SHARP_PATH=/app/node_modules/sharp" in runner section

also if you use same image for deps, builder, and runner. I just add "RUN npm i sharp" in runner section to solved this.

[yashmalik23-weplay]

Hi @asrudii , can you share the full dockerfile, package.json and env file. I can't seem to fix this even after doing all the changes you mentioned.

[asrudii]

[rgembalik]

I, on the other end, simply had to add

ENV NEXT_SHARP_PATH=/app/node_modules/sharp

in my Dockerfile. Not sure why the app would otherwise complain that there is no sharp installed since it was already in the node_modules.

[denkochev]

The only thing that worked for me.

[ArsenKakasyan]

solved for me

[rusakovic]

chm. what is missing?

[vvbbnn00]

Referring to issue: #59516

I have solved by downgrading sharp into 0.32.6

[alimoli]

I can confirm it and this doesn't need any env variable to work.
Thank you for that 🙏

[StevenMarrocco]

thank you! this worked for us as well

[Kikobeats]

It should be possible to use the latest sharp version, can you give a try? 🙏

[emredoganm]

Thank you @vvbbnn00 it does work for me 💃🏻

[Getitdan]

Can confirm it works. Add this to your Dockerfile: RUN yarn add sharp@0.32.6 --ignore-engines

[Pfed-prog]

ENV NEXT_SHARP_PATH=/dspyt/node_modules/sharp

worked for me

[Kikobeats]

If you are stuck on an old version of sharp (like 0.32.6), I have news for you: The Vercel team has fixed things that prevented newer versions of sharp from working.

I just shipped a project using the latest sharp version (sharp@0.33.2) and it worked fine 🙂 .

[AmirHosseinKarimi]

I use sharp@0.33.2 and it doesn't work.

[rvuyyuru2]

yes same for me as well

[styfle]

This should be fixed now on canary. You can try it out with npm i next@canary

[AmirHosseinKarimi]

When will it be applied to the stable version?

[styfle]

Its on stable in next@14.1.4

[ltbittner]

I can not get sharp 0.33.2 to work for the life of me. I'm on next@canary and I've tried every single trick I've found online, and no matter what it does not work. Quite frustrating

[abhithkba]

Doing these 2 steps helped me solve the issue :

1. Using sharp version 0.32.6

2. Add ENV NEXT_SHARP_PATH /app/node_modules/sharp to the Dockerfile.

[ramyNiranjan]

This works for me as well

[yoonnokdoo]

Thanks!

[hcastillaq]

yes, it work

[longnguyendev]

@abhithkba yes, it work thank a lot form VietNam with love

[xereda]

In which phase of the Dockerfile should I add the environment variable? Build or runner?

[abhithkba]

I did for Runner

[xereda]

I did in both. Same error:

   ▲ Next.js 14.0.4
   - Local:        http://b2f3e2e633c1:3000
   - Network:      http://172.17.0.2:3000

 ✓ Ready in 435ms
 ⨯ Error: 'sharp' is required to be installed in standalone mode for the image optimization to function correctly. Read more at: https://nextjs.org/docs/messages/sharp-missing-in-production

[abhithkba]

Try using either sharp versions 0.32.6 , 0.33.0 or 0.33.1 .
Cuz latest version tend to be ineffective here.

The fix for the problem is now available in v14.0.5-canary.60 of Next.js where you can use latest sharp package.

[xereda]

I adjusted it leaving the version fixed to 0.32.6. It worked! 👏🏻 🥳

[alexanderkhivrych]

did not work for me :(

[CaptainN]

Sometimes you can run in to trouble from an annoying npm bug (if you are using npm, instead of really anything better, like yarn or pnpm, or bun - anything) - basically, if you have a partial of optional deps in your node_modules folder on like an M1 (which means you don't have binaries for other platforms like linux/x86 - this is normal, usually npm will only add the optional dep you need to node_modules), and then you do npm i - it'll actually remove the unused optional packages from your package-lock.json file.

Why does it do this? Because npm.

Anyway, the fix is easy - delete node_modules, and package-lock.json and reinstall with no node_modules, to avoid npm getting confused. Then it will put the missing optional packages in your package-lock.json file. Then all you have to do is remember to do this whenever you add or change anything in your packages... This has worked for me almost every time when I'm forced to use npm. But really, just use anything else other than npm...