neo4j/docker-neo4j

chown: changing ownership of '/var/lib/neo4j/conf/neo4j.conf': Read-only file system

robertluoxu opened this issue · 3 comments

Guidelines

version: neo4j:4.4.7
docker: Docker version 20.10.21

  spec:
      containers:
        - image: neo4j:4.4.7
          imagePullPolicy: IfNotPresent
          name: container-0
          securityContext:
            allowPrivilegeEscalation: true
            privileged: false
            readOnlyRootFilesystem: false
            capabilities: {}
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
          volumeMounts:
            - mountPath: /var/lib/neo4j/data
              name: vol-wpgyk
            - mountPath: /var/lib/neo4j/conf
              name: vol-nlmes
          __active: true

logs :

chown: changing ownership of '/var/lib/neo4j/conf/..2023_05_06_06_51_54.97930143/neo4j.conf': Read-only file system
Sat, May 6 2023 2:53:38 pm | chown: changing ownership of '/var/lib/neo4j/conf/..2023_05_06_06_51_54.97930143': Read-only file system
Sat, May 6 2023 2:53:38 pm | chown: changing ownership of '/var/lib/neo4j/conf/..data': Read-only file system
Sat, May 6 2023 2:53:38 pm | chown: changing ownership of '/var/lib/neo4j/conf/neo4j.conf': Read-only file system
Sat, May 6 2023 2:53:38 pm | chown: changing ownership of '/var/lib/neo4j/conf': Read-only file system

ok so is this an actual error or just a warning? Does it fail to start?

The data volume should be mounted to /data not /var/lib/neo4j/data and the conf volume should be mounted to /conf not /var/lib/neo4j/conf