Title: feat: let self-hosted instances require custom deploy base images (FIPS / hardened) · Issue #5004 · triggerdotdev/trigger.dev · GitHub
Open Graph Title: feat: let self-hosted instances require custom deploy base images (FIPS / hardened) · Issue #5004 · triggerdotdev/trigger.dev
X Title: feat: let self-hosted instances require custom deploy base images (FIPS / hardened) · Issue #5004 · triggerdotdev/trigger.dev
Description: Is your feature request related to a problem? Please describe. Self-hosted operators inside a FedRAMP boundary must run task code on a FIPS-validated cryptographic module (NIST SC-13). For Node, that means building on a FIPS base image s...
Open Graph Description: Is your feature request related to a problem? Please describe. Self-hosted operators inside a FedRAMP boundary must run task code on a FIPS-validated cryptographic module (NIST SC-13). For Node, th...
X Description: Is your feature request related to a problem? Please describe. Self-hosted operators inside a FedRAMP boundary must run task code on a FIPS-validated cryptographic module (NIST SC-13). For Node, th...
Opengraph URL: https://github.com/triggerdotdev/trigger.dev/issues/5004
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"feat: let self-hosted instances require custom deploy base images (FIPS / hardened)","articleBody":"### Is your feature request related to a problem? Please describe.\n\nSelf-hosted operators inside a FedRAMP boundary must run task code on a FIPS-validated cryptographic module (NIST SC-13). For Node, that means building on a FIPS base image such as Chainguard `node-fips`. Stock Node statically links OpenSSL and can't run in FIPS mode.\n\nThe deploy base image is hard-pinned per runtime in [`BASE_IMAGE`](https://github.com/triggerdotdev/trigger.dev/blob/eb04c3191e3698c3ec4e07fb384c1ed3d9855923/packages/cli-v3/src/deploy/buildImage.ts#L711-L720) and [`BUILD_IMAGE`](https://github.com/triggerdotdev/trigger.dev/blob/eb04c3191e3698c3ec4e07fb384c1ed3d9855923/packages/cli-v3/src/deploy/buildImage.ts#L722-L731). Build extensions can't replace it. Today the only option is to `yarn patch` the CLI.\n\n#5002 proposes a per-project `trigger.config.ts` option. That would expose the setting to every Cloud user, and the Cloud team would then have to support arbitrary base images and would lose the shared-layer caching from #4602. This issue proposes an instance-operator setting instead.\n\n### Describe the solution you'd like to see\n\nA webapp setting that only self-hosted operators can set. Cloud never sets it, so nothing changes there.\n\n```bash\nDEPLOY_BASE_IMAGES=\"node-26=registry.example.com/node-fips:26@sha256:...\"\nDEPLOY_BUILD_BASE_IMAGES=\"node-26=registry.example.com/node:26-dev@sha256:...\" # optional\n```\n\n1. The webapp returns `baseImages` for the deployment's runtime in the initialize-deployment response, next to the existing `imagePlatform` and `externalBuildData`.\n2. The CLI rewrites the generated Containerfile to build on those images. Runtimes without an entry keep the published bases.\n3. Docs describe what a base image must provide: `node` at the runtime's major version, the [`DEFAULT_PACKAGES`](https://github.com/triggerdotdev/trigger.dev/blob/eb04c3191e3698c3ec4e07fb384c1ed3d9855923/packages/cli-v3/src/deploy/buildImage.ts#L734), a `node` user, and glibc. They also note that the apt-based extensions assume Debian.\n\nBecause the operator sets the base on the server, it applies to every deploy to the instance regardless of project config. For compliance, that is stronger than relying on each project to opt in.\n\n### Describe alternate solutions\n\n- **Per-project `build.image.base` in `trigger.config.ts`** (#5002 / #5003). It's simpler, but it exposes the option to Cloud users.\n- **`yarn patch` the `BASE_IMAGE` constant.** It works, but has to be redone on every CLI release.\n- **Swap the base with `image.instructions`, or rewrite the image after push.** Neither works: instructions run inside `FROM base`, and finalize records the digest before anything could change it.\n\n### Additional information\n\n- Draft implementation: see the linked PR. It reuses the existing initialize-deployment round trip, and the CLI only rewrites the Containerfile when the server sends `baseImages`.\n- Related: #5002 (per-project alternative), #1210 (self-hoster who needed a CA-cert hook and patched CLI internals), #4602 (introduced the pinned prebuilt bases).\n- This applies to any regulated self-hoster (FedRAMP, DoD IL, HIPAA/PCI hardening, internal golden images).\n","author":{"url":"https://github.com/brentshulman-silkline","@type":"Person","name":"brentshulman-silkline"},"datePublished":"2026-10-05T22:31:22Z","url":"https://github.com/triggerdotdev/trigger.dev/issues/5004"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react-reconciler,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@d5750093facf |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:7b73568a-4657-f0bd-fed6-d0ea9912bab2 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 8622:2CC06B:59E9DD1:7865699:6AFADE4D |
| html-safe-nonce | d996e8224b15d7c5f163a0116a4c1c37f9f4b256e10876573c42ff3b9784abf3 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4NjIyOjJDQzA2Qjo1OUU5REQxOjc4NjU2OTk6NkFGQURFNEQiLCJ2aXNpdG9yX2lkIjoiNzg1MDIyODUzNDA3MTcxMzM1NyIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | cd81a2c2672186e77e34fafbc208cbfe7f361f3e848d0f3b83dafe898296334a |
| hovercard-subject-tag | issue:5719827142 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/triggerdotdev/trigger.dev/5004/issue_layout |
| twitter:image | https://opengraph.githubassets.com/bea2874e67fa7713b074e41ea2bfd33f2bbbd3b6d48660c41f1d180933c3a9b0/triggerdotdev/trigger.dev/issues/5004 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/bea2874e67fa7713b074e41ea2bfd33f2bbbd3b6d48660c41f1d180933c3a9b0/triggerdotdev/trigger.dev/issues/5004 |
| og:image:alt | Is your feature request related to a problem? Please describe. Self-hosted operators inside a FedRAMP boundary must run task code on a FIPS-validated cryptographic module (NIST SC-13). For Node, th... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | brentshulman-silkline |
| hostname | github.com |
| expected-hostname | github.com |
| None | 9d9bd51a568909a83d1abb9d6f74d68f0c87ca85fe3a56d3f5d70d8b89add9f2 |
| turbo-cache-control | no-preview |
| go-import | github.com/triggerdotdev/trigger.dev git https://github.com/triggerdotdev/trigger.dev.git |
| octolytics-dimension-user_id | 95297378 |
| octolytics-dimension-user_login | triggerdotdev |
| octolytics-dimension-repository_id | 572570113 |
| octolytics-dimension-repository_nwo | triggerdotdev/trigger.dev |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 572570113 |
| octolytics-dimension-repository_network_root_nwo | triggerdotdev/trigger.dev |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 4a7ae932999cc6d511008dbf980ff9efad2a31f7 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width