Skip to content

Commit 6283966

Browse files
Yanchek99claude
andauthored
Fix production boot crash: install libffi8 in Railway runtime image (#1869)
* Fix production boot crash: install libffi8 in Railway runtime image web and worker have been crashing on boot since 2026-08-19 with LoadError: libffi.so.8: cannot open shared object file, from the ffi gem's native extension (required transitively via sassc -> sassc-rails). Railpack doesn't auto-detect libffi as a runtime dependency for Ruby's ffi gem, and something changed on Railway's builder side that stopped carrying libffi.so.8 into the deploy image. Explicitly declaring it in railpack.json's deploy.aptPackages restores it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> * Document why libffi8 is needed in railpack.json Explains the ffi -> sassc -> sassc-rails -> rails_admin chain and the Railpack v0.37.0 Debian 13 migration that dropped libffi.so.8 from the runtime image, so this doesn't look like an arbitrary apt package pin. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
1 parent 8938dc4 commit 6283966

1 file changed

Lines changed: 13 additions & 0 deletions

File tree

railpack.json

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
{
2+
"$schema": "https://schema.railpack.com",
3+
"deploy": {
4+
// The ffi gem (native ext, required via sassc -> sassc-rails, which
5+
// rails_admin's Sprockets asset pipeline needs) links against
6+
// libffi.so.8 at boot. Railpack doesn't auto-detect libffi as a
7+
// runtime dependency, and Railpack v0.37.0's move to Debian 13
8+
// (Trixie) base images stopped carrying it into the deploy image,
9+
// crashing web and worker on boot. "..." extends Railpack's
10+
// auto-detected apt package list rather than replacing it.
11+
"aptPackages": ["...", "libffi8"]
12+
}
13+
}

0 commit comments

Comments
 (0)