docker: pre-install the duckdb aws extension#111
Merged
Conversation
CREATE SECRET (TYPE s3, PROVIDER credential_chain) — the Pod-Identity path the composition-stamped tenant maintenance crons use — requires the aws extension. It was never pre-installed, so DuckDB attempted a runtime auto-install, which dies on the crons' read-only root filesystem: Cannot open file ".../.duckdb/extensions/v1.5.2/linux_arm64/ aws.duckdb_extension.tmp-...": Read-only file system The central viaduck crons never hit this: they authenticate with static env credentials, which need no aws extension. Same first-time-exercised class as the psql gap (#110): observed live on the first tenant cron run that got past bootstrap-indexes.
jghoman
force-pushed
the
jakob/preinstall-aws-extension
branch
from
July 24, 2026 17:33
0091f08 to
65ce417
Compare
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.
CREATE SECRET (TYPE s3, PROVIDER credential_chain)— the Pod-Identity path the composition-stamped tenant maintenance crons use — requires DuckDB'sawsextension. It was never in the build-time pre-install set (httpfs/ducklake/postgres), so DuckDB attempts a runtime auto-install, which dies on the crons' read-only root filesystem:The central viaduck crons never exercised this path — they authenticate with static env credentials, which need no aws extension. Same first-time-exercised class as the psql gap (#110): observed live on the first tenant cron run to get past
bootstrap-indexes(psql now works fleet-wide, so #110 is confirmed in prod).With the image now floating on
:prod(charts #13475), a release after merge reaches every tenant cron on its next tick — no chart change.