You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a new container and passing the configuration file (-v neo4j.conf:/var/lib/neo4j/conf/neo4j.conf) will result in overwriting my changes and reverting back to default.
Trying to play "smartass" and setting the file as read only will result in neo4j container restarting complaining that the file is read only.
Using the default neo4j:3.1.2 image from dockerhub
And tried also with neo4j:3.2.1 as well - same issue.
The text was updated successfully, but these errors were encountered:
I checked the entry-point file in the dockerbuild and found out that /conf is being copied to /var/lib/neo4j/conf - so I've mounted my configuration file at /conf and that solved the issue.
When running a new container and passing the configuration file (
-v neo4j.conf:/var/lib/neo4j/conf/neo4j.conf
) will result in overwriting my changes and reverting back to default.Trying to play "smartass" and setting the file as read only will result in neo4j container restarting complaining that the file is read only.
Using the default neo4j:3.1.2 image from dockerhub
And tried also with neo4j:3.2.1 as well - same issue.
The text was updated successfully, but these errors were encountered: