docker-neo4j: Can't override heap configuration
I have tried everything at this point:
- -v /docker-store/neo4j/conf:/conf
- -v /docker-store/neo4j/conf:/var/lib/neo4j/conf
- -v /docker-store/neo4j/conf/neo4j.conf:/conf/neo4j.conf
- -v /docker-store/neo4j/conf/neo4j.conf:/var/lib/neo4j/conf/neo4j.conf
- Edit /conf/neo4j.conf in vi, commit container and launch the new container
Nothing seems to stick, and this works for pretty much every other docker image I have ever used.
I saw another person had the issue, but was not able to successfully use their solution: https://github.com/neo4j/docker-neo4j/issues/95
- System: Ubuntu 18.04 x86_64
- Docker Version:
ii docker-ce 5:18.09.0~3-0~ubuntu-bionic amd64 Docker: the open-source application container engine
ii docker-ce-cli 5:18.09.0~3-0~ubuntu-bionic amd64 Docker CLI: the open-source application container engine
- Docker Launch Script:
#!/bin/bash
docker run --name neo4j --restart=unless-stopped -p 7474:7474 -p 7687:7687 \
-v /docker-store/neo4j/conf:/conf \
-v /docker-store/neo4j/data:/data \
--user 1000 -d neo4j
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 18 (6 by maintainers)
I had similar issues and just want to take a moment to politely curse Neo4j for the double
__
in this value:NEO4J_dbms_memory_heap_max__size
😄@csvance @chrstnb @slothkong Sorry for taking so long to tackle this issue. It should have been fixed by: #180 This fix is in the 3.5.7 release. Do you still have the problem if you use a neo4j 3.5.7 image?