Closed j616 closed 4 years ago
@j616 I tried running your reproduction code, but Neo4j 4.0.7 started as expected:
docker-compose up
Starting 269-permission-onstart_neo4j_1 ... done
Attaching to 269-permission-onstart_neo4j_1
neo4j_1 | Changed password for user 'neo4j'.
neo4j_1 | Fetching versions.json for Plugin 'apoc' from https://neo4j-contrib.github.io/neo4j-apoc-procedures/versions.json
neo4j_1 | Installing Plugin 'apoc' from https://github.com/neo4j-contrib/neo4j-apoc-procedures/releases/download/4.0.0.17/apoc-4.0.0.17-all.jar to /var/lib/neo4j/plugins/apoc.jar
neo4j_1 | Applying default values for plugin apoc to neo4j.conf
neo4j_1 | Skipping dbms.security.procedures.unrestricted for plugin apoc because it is already set
neo4j_1 | Directories in use:
neo4j_1 | home: /var/lib/neo4j
neo4j_1 | config: /var/lib/neo4j/conf
neo4j_1 | logs: /logs
neo4j_1 | plugins: /var/lib/neo4j/plugins
neo4j_1 | import: /var/lib/neo4j/import
neo4j_1 | data: /var/lib/neo4j/data
neo4j_1 | certificates: /var/lib/neo4j/certificates
neo4j_1 | run: /var/lib/neo4j/run
neo4j_1 | Starting Neo4j.
neo4j_1 | 2020-07-22 12:03:10.199+0000 INFO ======== Neo4j 4.0.7 ========
neo4j_1 | 2020-07-22 12:03:10.205+0000 INFO Starting...
neo4j_1 | 2020-07-22 12:03:18.717+0000 INFO Called db.clearQueryCaches(): Query cache already empty.
neo4j_1 | 2020-07-22 12:03:18.787+0000 INFO Bolt enabled on 0.0.0.0:7687.
neo4j_1 | 2020-07-22 12:03:18.788+0000 INFO Started.
neo4j_1 | 2020-07-22 12:03:19.516+0000 INFO Remote interface available at http://localhost:7474/
There are a couple of similar sounding active issues that you may be hitting though:
Warning: Folder mounted to "/data/dbms" is not writable from inside container. Changing folder owner to neo4j.
and Caused by: java.io.FileNotFoundException: /logs/debug.log
would suggest that there are /data
and /logs
folder being mounted.So, my questions:
NEO4JLABS_PLUGINS
?Hello, thanks for your reply. I've managed to solve my issue by pruning containers. But for completeness:-
docker-compose.yml
file or in the commands I'm using to start the containers.
version: '3.8'
services: neo4j: image: neo4j:4.0 environment:
The specific commands I was using to start the container:-
docker-compose -f ./docker-tests/docker-compose.yml pull
docker-compose -f ./docker-tests/docker-compose.yml up
The pull being there to make sure I get the latest version, even if I already have on that satisfies the requirements available on my machine.
If you have any thoughts on why the prune would be needed in this case, I'd be grateful. But appreciate that "go and google it" is a legitimate reply :sweat_smile:
Thanks for your help.
That is weird. Maybe one of the docker layers got corrupted/corrupted itself somehow? I would have thought that if there are no shared mounts, then two running containers would be isolated and not break each other, but I don't know the specifics of how docker caching works. Maybe I've been making an assumption that containerisation (and linux namespacing) automatically gives you compartmentalistaion for free.
I didn't have any other instances running so I don't think it'd be that. If anything, it'd be a between launches issue rather than a between running instances issue.
It could be that one of the Dockerfiles up the stack isn't invalidating the layer cache correctly? So a new version isn't being pulled because docker doesn't think there's been any changes at that layer? But purging will force the whole stack to be pulled. I know that can cause issues when building a container locally. I'm not sure if it can also cause an issue once deployed to the repositories.
Same happened to me, pruning solved the issue
Problem
The neo4j Docker image has started failing to start with a permissions error on logs. I'm specifying version
4.0
which currently maps to4.0.7
. I am not mapping any volumes. My builds worked yesterday when4.0.6
was the latest4.0
version.Steps to reproduce
Relevant docker-compose:-
Expected behaviour
Neo4j Docker container starts.
Actual behaviour
Container fails to start with the following output:-
Neo4j image tag being used, eg
neo4j:latest
,neo4j:enterprise-3.5
etcneo4j:4.0
The output of the
docker version
commandOperating system: (for example Windows 95/Ubuntu 16.04)
Ubuntu 18.04