Skip to content

Commit e5023ab

Browse files
committed
fix: take chromium from nix, not ubuntu's snap stub
1 parent dd70b03 commit e5023ab

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

‎nixpacks.toml‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,10 @@
44
# agent turn could start in production. Declaring it here puts a real binary
55
# on PATH instead.
66
[phases.setup]
7-
nixPkgs = ["nodejs_24", "pnpm"]
87
# Project covers are screenshots, and puppeteer's own Chrome download never
98
# happens here — so it launched nothing and every project stayed coverless.
10-
# Debian's build brings its shared libraries with it, which the Chrome-for-
11-
# Testing tarball does not on this image. The start command points puppeteer
12-
# at it; see railway.json.
13-
aptPkgs = ["chromium"]
9+
# It comes from nix rather than apt because this base image is Ubuntu, whose
10+
# `chromium` package is only a stub that installs a snap at first run: the
11+
# binary exists but refuses to start inside a container. The start command
12+
# points puppeteer at whatever this puts on PATH; see railway.json.
13+
nixPkgs = ["nodejs_24", "pnpm", "chromium"]

0 commit comments

Comments
 (0)