Add nixpacks.toml to bypass Dockerfile for Go build - #1
Open
Hewlbern wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Problem
Builds fail immediately after "scheduling build on Metal builder" with no compile logs and eventually time out. The service has both a Dockerfile (dockerfilePath: "Dockerfile") and Railpack configured, and the multi-stage Dockerfile causes the Metal builder to hang silently with no output, even though the Go source compiles fine locally.
Solution
Added a nixpacks.toml at the repository root (alongside go.mod) that explicitly declares the Go provider and defines the build and start commands, taking precedence over the Dockerfile. The build phase runs
CGO_ENABLED=0 GOOS=linux go build -o /tmp/solidgo ./cmd/server, and the start command runs the compiled binary with the port and storage path derived from PORT, SOLID_PORT, and SOLID_STORAGE_PATH, matching the flags already read in cmd/server/main.go.Changes
nixpacks.tomlGenerated by Railway