Favicon not found with file-based metadata in standalone build

[BigOoga]

Verify canary release

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

Provide environment information

Operating System:
      Platform: linux
      Arch: x64
      Version: #67-Ubuntu SMP Mon Mar 13 14:22:10 UTC 2023
    Binaries:
      Node: 16.19.0
      npm: 8.19.3
      Yarn: 1.22.19
      pnpm: 7.21.0
    Relevant packages:
      next: 13.3.1-canary.18
      eslint-config-next: 13.3.1
      react: 18.2.0
      react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Metadata (metadata, generateMetadata, next/head, head.js), Standalone mode (output: "standalone")

Link to the code that reproduces this issue

https://github.com/BigOoga/standalone-metadata-bug

To Reproduce

Run docker-compose up --build to build the image and run the container

Describe the Bug

Going by the error
Error: ENOENT: no such file or directory, open '/app/src/app/favicon.ico'
The server tries to open the image path as if running the server with next start.

Expected Behavior

I'd expect the standalone build to correctly bundle the favicon and correctly path to it.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

dockerized standalone build

[masterkain]

same issue

[sFritsch09]

#49107

[sidmclaughlin]

As of Next.js 13.3.4, the standalone output doesn't properly copy the favicon, and instead expects it to be present at the same path as during the build phase.

A quick workaround is to add a COPY to your runner phase, mimicking the same path as provided in the error.

COPY --from=builder --chown=nextjs:nodejs /app/src/app/favicon.ico ./src/app/favicon.ico

Brief discussion: #41745 (comment)
Repro w. fix: https://github.com/sidmclaughlin/nextjs-favicon-repro (see Dockerfile-broken, Dockerfile-fixed)

[sFritsch09]

My working Dockerfile 🐳:

# dependencies image
FROM node:20-alpine AS deps
WORKDIR /app
COPY package.json yarn.lock ./
RUN yarn install --frozen-lockfile

# build image
FROM node:20-alpine AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .
RUN yarn build

# build output image
FROM node:20-alpine AS run
ENV NODE_ENV production
RUN addgroup -g 1001 -S nodejs
RUN adduser -S nextjs -u 1001
WORKDIR /app
COPY --from=builder --chown=nextjs:nodejs /app/package.json /app/yarn.lock ./
COPY --from=builder --chown=nextjs:nodejs /app/node_modules ./node_modules
COPY --from=builder --chown=nextjs:nodejs /app/public ./public
COPY --from=builder --chown=nextjs:nodejs /app/.next ./.next
COPY --from=builder --chown=nextjs:nodejs /app/app/favicon.ico ./app/favicon.ico
COPY --from=builder --chown=nextjs:nodejs /app/app/icon.png ./app/icon.png
COPY --from=builder --chown=nextjs:nodejs /app/app/opengraph-image.jpg ./app/opengraph-image.jpg
COPY --from=builder /app/next.config.js ./next.config.js
USER nextjs
EXPOSE 3000
CMD [ "yarn", "start" ]

[huozhi]

We got a fix out in 13.4, upgrade it to check it out if resolves the issue 🙏

[BigOoga]

We got a fix out in 13.4, upgrade it to check it out if resolves the issue pray

I updated and it's now working perfectly on my setup, thank you!

[github-actions]

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.