Repository navigation
[1.0] fix(ci): add .dockerignore to keep the build context limited to tracked files (#508) - #516
Merged
Merged
Conversation
… BC CVE cluster status (#508) ## Summary **Verification:** the fix for this Bouncy Castle CVE cluster is already on `main` (commit a19c933, "fix(deps): bump jruby-openssl to 0.16.2 for BC 1.85 CVE cluster", 2026-08-27): - `Dockerfile`/`Dockerfile.wolfi` strip the JRuby-stdlib-bundled BC jars (1.79, from jruby-openssl 0.15.3 shipped inside JRuby 9.4.12.0 itself) after install. - `Gemfile`/`Gemfile.lock` pin `jruby-openssl` to `0.16.2` (bundles BC 1.85). - `Jarfile`/`Jars.lock` pin `org.bouncycastle:*` directly to `1.85`. **The gap:** the last published release tag `v0.1.0` predates this fix (`git merge-base --is-ancestor a19c933 v0.1.0` → not an ancestor). The published `docker.elastic.co/integrations/crawler` image Snyk has been scanning was built before the fix landed — cutting a new release/tag from current `main` and republishing is still needed (not something this PR does). **Real fix included:** added a `.dockerignore` (none existed before). `Dockerfile`/`Dockerfile.wolfi` both do `COPY . /home/app`. Gems/jars install fresh inside the build (`script/bundle` -> `/usr/local/bundle`, `script/vendor_jars` -> `vendor/jars`), so nothing under the gitignored `vendor/bundle`, `vendor/ruby`, `vendor/jruby`, etc. is actually needed from the build context. Without a `.dockerignore`, a developer's stale local build state sitting in one of those gitignored directories would get copied verbatim into the image by `COPY . /home/app` — harmless at runtime, but still flaggable by filesystem-based scanners like Snyk (matching some of the `/home/app/vendor/...` paths in the original findings). Verified the Docker build still succeeds and produces a clean image with only the pinned `bcprov-jdk18on` 1.85 and `jruby-openssl` 0.16.2 present, no stray BC versions. Mirrors the `ent-search` fix in elastic/ent-search#8755 — same class of risk (stale local build state leaking into a shipped artifact), different packaging mechanism. ## related issues elastic/search-team#15610 elastic/search-team#15613 elastic/search-team#15614 elastic/search-team#15615 elastic/search-team#15616 elastic/search-team#15617 elastic/search-team#15618 elastic/search-team#15619 elastic/search-team#15620 elastic/search-team#15621 elastic/search-team#15622 elastic/search-team#15623 elastic/search-team#15624 elastic/search-team#15625 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com> Co-authored-by: Jan-Kazlouski-elastic <jan.kazlouski@elastic.co>
Jan-Kazlouski-elastic
enabled auto-merge (squash)
October 5, 2026 19:00
Jan-Kazlouski-elastic
approved these changes
Oct 5, 2026
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
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.
Backports the following commits to 1.0: