start with certain kinds of corruption?? WAS: Re:
[Neo4j] Neo4j failed to start under Docker: "Already closed exception"
But I know how to work around it for my particular case...
Remove all the files under /var/lib/neo4j/data/databases/graph.db (!)
That seems a little extreme
But I know how to work around it for my particular case...
Remove all the files under /var/lib/neo4j/data/databases/graph.db (!)
That seems a little extreme... But I didn't need that data for my
particular circumstance - so it works for me.
Presumably someone else will run into
Wrong. I didn't test what I thought I did - it's still broken - Sigh...
For some reason I didn't have the initial failure messages in the logs
below - but here are some additional messages.
[o.n.k.i.s.f.RecordFormatSelector] Selected
RecordFormat:StandardV3_0[v0.A.7] record format from store
It looks like this is some kind of bug related to Docker and apparmor.
Disabling apparmor makes it go away...
On 09/01/2016 11:11 AM, Alan Robertson wrote:
> Hi,
>
> I've been having trouble with getting Neo4j to start in a docker
> image. This image was produced by a Dockerfile which built my