Close immediately after change password log

[ak-seyam]

Note: this behavior is random I've restarted it 3 times it didn't work the 4th one it worked as expected

• Steps to reproduce.
  I've written this docker-compose

  neo4j:
    image: neo4j:4.4.0
    environment:
      - NEO4J_AUTH=neo4j/pass
    volumes:
      - ./persistance/data:/data
      - ./persistance/logs:/logs
      - ./persistance/import:/var/lib/neo4j/import
      - ./persistance/plugins:/plugins
    ports:
      - "7474:7474"
      - "7687:7687"

• Expected behavior: to start normally
• Actual behavior:

neo4j_1         | Changed password for user 'neo4j'.
tst-api_neo4j_1 exited with code 1

• *Neo4j image tag being used, eg neo4j:latest, neo4j:enterprise-3.5 etc: neo4j:4.4.0
• The output of the docker version command:

Client: Docker Engine - Community
 Version:           20.10.12
 API version:       1.41
 Go version:        go1.16.12
 Git commit:        e91ed57
 Built:             Mon Dec 13 11:45:33 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.12
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.12
  Git commit:       459d0df
  Built:            Mon Dec 13 11:43:42 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.12
  GitCommit:        7b11cfaabd73bb80907dd23182b9347b4245eb5d
 runc:
  Version:          1.0.2
  GitCommit:        v1.0.2-0-g52b36a2
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

• Host operating system: ubuntu 20.04

Additionally, include (as appropriate) log-files, stacktraces, and other debug output: the /logs/debug.log (./persistance/logs/debug.log on my host machine) is empty

[jennyowen]

I was able to run docker-compose from the code you gave, but it started Neo4j fine every time I ran it.

It is interesting that the changed password message seems to come from a container called neo4j_1 but the exited message comes from a container called tst-api_neo4j_1. Could it be that you have 2 neo4j containers running at the same time, possibly sharing volume mount folders?

[cosmeowpawlitan]

I encounter the same issue multiple times, but when I rebuild the container with the same configuration, the issue is gone.