Skip to content

Stop Neo4j dying on a modern host kernel #79

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adamjohnwright merged 1 commit into from
Sep 15, 2026
Merged

Stop Neo4j dying on a modern host kernel #79

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,11 @@ services:
- "7687:7687" # Bolt
environment:
- NEO4J_dbms_memory_heap_maxSize=8g
# This image ships JDK 11, whose container-metrics probe NPEs reading
# cgroup v2 on a newer host kernel — Neo4j then dies before startup with
# ExceptionInInitializerError out of CgroupV2Subsystem.getInstance. The
# heap is pinned above, so container-aware sizing buys nothing here.
- NEO4J_dbms_jvm_additional=-XX:-UseContainerSupport
volumes:
- neo4j_data:/data
- neo4j_logs:/logs
Expand Down
Loading