How NEO4J_ALLOW_STORE_UPGRADE should be used ? about docker-neo4j

[benbc]

Hello @sgrunt91. I'm sorry you're having trouble with this.

The NEO4J_ALLOW_STORE_UPGRADE feature is not yet available for the neo4j image in the official image library. It's only available in the image in our own repo on Docker Hub (i.e. neo4j/neo4j).

Are you able to use that instead?

The feature will be part of the next release to the official image library (2.3.2), but we don't have a date for that yet.

[sgrunt91]

Hello @benbc ,

Oh :( Well, I'm too hasty, I'll wait for it!

For now I change my container with using neo4j/neo4j:2.2.7 which is my actual database version, so no need to use this variable.
I wanted to benefit from the docker migration to do a Neo4j version upgrade, but I can wait.
There are another environnement variables that not available yet ?

I guess it shows, I'm new to docker, and I hadn't understand the difference between official library and your repo, for me neo4j was the same that neo4j/neo4j, but if I understand neo4j is the release of a last neo4j/neo4j ? so there a delta between them.
I'm confused.

So, I think you could close this if you want. My bad...

Thanks again!
Regards,

[benbc]

You'll see that the documentation for the official image (neo4j, here) and the image in our repo (neo4j/neo4j, here) is identical except for this one feature, so it's understandable that you were confused.

If you're on 2.2.7 then you'll need to get that from neo4j/neo4j anyway. When you get round to upgrading to 2.3.1, you'll find that NEO4J_ALLOW_STORE_UPGRADE works fine if you use neo4j/neo4j; and if 2.3.2 is out by the time you upgrade then it'll work for neo4j too.