Failed to update prerender cache for /index

[mo-alaa]

Summary

Hi! I have a problem in the logs. I am implementing ISR with getStaticProps.
For the exact pages the have ISR, I found this error:

Failed to update prerender cache for /index [Error: EACCES: permission denied, open '/app/.next/server/pages/index.html'] {
errno: -13,
code: 'EACCES',
syscall: 'open',
path: '/app/.next/server/pages/index.html'
}

I use Docker, with a similar multi-stage deployment like in this example

I tried several approaches, like:

• Upgrading nextJs to the latest version.

• Copying the whole next directory in the last build stage, runner (instead of the static directory only)
  COPY --from=builder --chown=nextjs:nodejs /app/.next ./.next

• I created the pages directory and gave permissions write (during the runner stage with the root user)
  RUN mkdir -p /app/.next/server/pages
RUN chmod 777 /app/.next/server/pages

• I even created the html page and gave it users permissions to write and execute, till my last build stage (runner) looked like this:
  

Do you have any idea what is the cause of the error or how it can be resolved ?
Thanks!

Additional information

No response

Example

No response

[devjiwonchoi]

Try User node since the node user is provided in the Node.js Alpine base image.

Reference

• What is the best way to use NextJS with docker? #16995

[mo-alaa]

@devjiwonchoi Hmm It didn't work. However, the only thing that removed the error was giving the server directory recursive read/write/exec permissions for others like so:
RUN mkdir -p /app/.next/server
RUN chmod -R 777 /app/.next/server

The weird thing is that 770, 775 and 776 didn't work, this means it needs read, write and execute permissions to "other users".

Which makes me wonder how can I know which user needs this. I know it is not the node user because I changed ownership to the node user but it gave the same error:
RUN mkdir -p /app/.next/server
RUN chown -R node /app/.next/server
RUN chmod -R 770 /app/.next/server

and I was sure the the user is node:
USER node

[mo-alaa]

Of course the above solution opens a security concern! So it doesn't solve the problem.
I also wonder how does it give that error while the application actually revalidates and gets the new updates from CMS!

[8lane]

Seeing this exact issue as well with NextJs 13.4.12 using a mix of app router and pages router. All static routes give the Failed to update prerender cache error on first load after running the docker container.

[biohackerellie]

adding on to this, in my project also deployed in docker fully using app router, I'm getting similar errors

 errno: -13,
  code: 'EACCES',
  syscall: 'mkdir',
  path: '/app/.next/cache/fetch-cache

and i do have this in my dockerfile

RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/public ./public
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
COPY --from=builder --chown=nextjs:nodejs /app/.next/cache ./.next/cache
USER nextjs

[ghost]

Did you happen to find any futher updates on this? Experiencing currently with 13.4.19 when running containerized build.

[mo-alaa]

No updates yet, unfortunately.

[teguh77]

this error still exists, Does anyone already know the solution?

[taymoork2]

So a potential solution could be that your docker/kubernetes setup is not configured to run as a NonRoot user along with the correct nonroot user id for it to use.
This seemed to be the issue with my orgs internal infra setup that some configurations weren't setup for my specific deployments to use a nonrootuser

[sachin36987]

Adding the following lines before copying from builder and chown fixed the issue for me

RUN mkdir .next
RUN chown nextjs:nodejs .next