You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b5ed66b
Browse filesBrowse the repository at this point in the historyBrowse files
fix(cli): keep custom base images' own trust store
Fixes `trigger deploy` failing on self-hosted instances that set custom
base images with `DEPLOY_BASE_IMAGES` or `DEPLOY_BUILD_BASE_IMAGES`
(#5054). The deploy step that distrusts compromised emSign certificate
authorities assumed the published root Debian images, so it broke on
non-root or non-Debian bases such as Chainguard's.
Stages built on a custom image now skip that step and keep the
certificate settings the image ships with. Stages on the published
images are unchanged. The self-hosting docs now state that a custom base
image owns its own security hardening.
Mono-RevId: 5de0cdda76e9b57d7b076d52c6ab8c763934e2d3
Fix `trigger deploy` failing on self-hosted instances with custom base images. Stages built on a custom image now keep the trust store that image ships with.
Copy file name to clipboardExpand all lines: docs/self-hosting/overview.mdx
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,6 +121,8 @@ You own a custom base image. It must provide:
121
121
122
122
A `DEPLOY_BUILD_BASE_IMAGES` image needs everything the base image provides, plus `python3`, `make` and `g++`. Build extensions that add image instructions are replayed on it. Without an entry, the build stage uses the published build image, except for projects whose build extensions add image instructions: those build from your base image and install the toolchain with `apt-get`, so that base must be Debian-based. To avoid the published images entirely, set both variables.
123
123
124
+
A custom image is yours to harden. Deploys on the published images remove trust in publicly compromised certificate authorities and point Node.js and Python at the OS trust store. Stages built on a custom image get neither, and run with the certificate settings the image ships with. Keeping a custom image patched, trust store included, is your responsibility.
125
+
124
126
<Warning>
125
127
`image.pkgs` and build extensions that run `apt-get` (such as `aptGet` and `playwright`) assume a
126
128
Debian base. On other distributions, install those packages in your base image instead.
0 commit comments