Issue Station
Sign In
Tools hereToolbox

nextjs - ✅(Solved) Fix Docs: Update `with-docker` example to not use standalone server or update documentation [1 pull requests, 8 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#88885•Fetched 2026-04-08 02:03:45
View on GitHub
Comments
8
Participants
2
Timeline
25
Reactions
1
Author
Luk-zLuk-z
Participants
icyJosephicyJosephLuk-zLuk-z
Assignees
icyJosephicyJoseph
Timeline (top)
commented ×8subscribed ×6mentioned ×4referenced ×3

Error Message

If this is not an error maybe you could write a minimal docs on why it is used with Dockerfile.

Fix Action

Fixed

PR fix notes

PR #89778: docs: add Docker standalone output guidance to deploying and self-hosting guides

Description (problem / solution / changelog)

What?

Add standalone output mode explanation and inline examples to the deploying and self-hosting documentation.

Why?

The with-docker example already uses output: "standalone", but the deploying and self-hosting docs did not explain this configuration or why it's recommended for Docker deployments. This caused confusion for users trying to containerize their Next.js applications (see #88885).

How?

docs/01-app/01-getting-started/17-deploying.mdx

  • Added "Using output: "standalone"" subsection under Docker
  • Included next.config.js configuration example
  • Added minimal Dockerfile snippet showing standalone usage
  • Added notes about alternatives (native binaries, simpler setup)
  • Added development tip about local development vs Docker

docs/01-app/02-guides/self-hosting.mdx

  • Added dedicated "Docker" section before "Environment Variables"
  • Explained standalone mode benefits (image size: ~110 MB vs ~1 GB)
  • Included HOSTNAME and PORT environment variable configuration
  • Added note about falling back to next start when needed

fixes #88885

Changed files

  • docs/01-app/01-getting-started/17-deploying.mdx (modified, +29/-0)
  • docs/01-app/02-guides/self-hosting.mdx (modified, +16/-0)
RAW_BUFFERClick to expand / collapse

What is the documentation issue?

Why with-docker example use standalone server but the docs say the opposite?

If this is not an error maybe you could write a minimal docs on why it is used with Dockerfile.

Is there any context that might help us understand?

Does the docs page already exist? Please link to it.

https://nextjs.org/docs/app/getting-started/deploying#docker

extent analysis

TL;DR

The documentation for Next.js deployment with Docker may need clarification on the use of a standalone server.

Guidance

  • Review the Next.js documentation on self-hosting and deploying with Docker to ensure consistency in the recommended approach.
  • Verify if the with-docker example is using a standalone server due to specific requirements that the integrated router cannot meet.
  • Check the custom server guide to understand the use cases where a standalone server is necessary.
  • Consider adding a note to the documentation to explain why a standalone server is used in the with-docker example.

Example

No code snippet is provided as it is not necessary for this documentation-related issue.

Notes

The issue seems to be related to inconsistent documentation, and resolving it may require updating the documentation to reflect the correct approach for deploying Next.js with Docker.

Recommendation

Apply workaround: Add a note to the documentation to clarify the use of a standalone server in the with-docker example, as it may be necessary for specific use cases.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#index setup#retrieval issue#search optimization#API routing#API middleware

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING