fix(docker): include next.config.ts in build context#171
Merged
Conversation
- .dockerignore *.ts rule excluded root-level next.config.ts from the image build context - Next.js built with default config, skipping output "standalone"; release image failed at COPY /app/.next/standalone
arbisoft-qaisarirfan
approved these changes
Jul 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 Description
Fix the container release build failing with
"/app/.next/standalone": not foundby re-includingnext.config.tsin the Docker build context.📌 Summary
.dockerignoreline 19 (*.ts) excludes root-level TypeScript files. When Sentry integration renamednext.config.js→next.config.ts(578d5b5), the config silently fell under this rule. The builder stage then rannext buildwith default config —output: "standalone"was never applied,.next/standalonewas never generated, and the runner stageCOPYatDockerfile:56failed. Releases v1.3.2 and v1.3.3 are both broken by this (v1.3.2 surfaced it as the missing sentry-config module, fixed in #170; v1.3.3 surfaced the standalone gap).