Skip to content

Update submodule version and previewed docker image#3

Merged
gaoxueyu merged 4 commits into
IvorySQL:mainfrom
NotHimmel:main
Jun 25, 2026
Merged

Update submodule version and previewed docker image#3
gaoxueyu merged 4 commits into
IvorySQL:mainfrom
NotHimmel:main

Conversation

@NotHimmel

Copy link
Copy Markdown
Collaborator

No description provided.

- Update ivy_duckdb submodule to 7a6d35e (origin/main, PR IvorySQL#3)
- Bump IVORYSQL_BASE to 5.4-ubi8 in Dockerfile
- Add Cargo.lock; update .gitignore
- Add ccache to the build toolchain; route C/C++ compiles through it
  via /usr/lib64/ccache in PATH (CCACHE_DIR=/ccache, MAXSIZE=10G)
- Cache-mount cargo registry/git and target/ so Rust deps and build
  artifacts persist across rebuilds
- Cache-mount /ccache on the DuckDB build so C++ objects survive layer
  invalidation
- Merge cargo pgrx package + artifact collection into one RUN, since the
  cache-mounted target/ is not persisted into the next image layer

First (cold) build is unchanged; subsequent rebuilds reuse cached objects.
Document registry.highgo.com/mooncake/ivy_mooncake:0.1 with a docker run
example covering ports, password, and data/warehouse volumes.
Routing cargo's cc-rs through the global-PATH ccache wrapper broke the
aws-lc-sys build: its prefixed .S assembly files fail under ccache with a
silent exit 1 (empty stderr). DuckDB is pure C++ and is unaffected.

Enable ccache only for `make ivy_duckdb` via an inline PATH, keep it off the
global PATH, and drop the now-unused /ccache mount from the cargo package
step. Rust dependencies remain cached via the target/ mount, so rebuild
speed is preserved while the package step uses the real compiler.

Verified: full image build succeeds, aws-lc-sys compiles, and the resulting
image runs pg_mooncake end-to-end.
@gaoxueyu gaoxueyu merged commit d0366e4 into IvorySQL:main Jun 25, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants