Memgraph can't start with volume in bind mode about memgraph

[katarinasupe]

So far, we recommended changing the default location of a docker data directory with the --data-root property. Here is more on that topic:
https://stackoverflow.com/questions/36014554/how-to-change-the-default-location-for-docker-create-volume-command

Let me know if that helps somehow.

We also had suggestions from our Discord community for workarounds (you can join there). For example, this is what a community member suggested for the Memgraph Platform (which can probably be applied to Memgraph image as well):

version: "3.9"
services:
  memgraph:
    image: memgraph/memgraph-platform:latest
    ports:
      - "7687:7687"
      - "3000:3000"
      - "7444:7444"
    volumes:
      - mg_lib:/var/lib
      - mg_log:/var/log
      - mg_etc:/etc/memgraph
    environment:
      - MEMGRAPH="--storage-properties-on-edges=true --log-level=TRACE"
    entrypoint: ["/usr/bin/supervisord"]
volumes:
  mg_lib:
    driver: local
    driver_opts:
      type: 'none'
      o: 'bind'
      device: 'path/on/host'
  mg_log:
    driver: local
    driver_opts:
      type: 'none'
      o: 'bind'
      device: 'path/on/host'
  mg_etc:
    driver: local
    driver_opts:
      type: 'none'
      o: 'bind'
      device: 'path/on/host'

Tbh, I haven't tried the above, and it should be tested, but I thought it's best I provide you with all the information I have. Here is the thread on Discord.

[vector-mj]

Thank you @katarinasupe, your Docker compose manifest worked for me.

version: '3.9'
services:
  memgraph:
    image: docker.arvancloud.ir/memgraph/memgraph-platform
    container_name: memgraph
    ports:
      - 7687:7687
      - 7444:7444
      - 3000:3000
    environment:
      MEMGRAPH: "--memory-limit=1000 --log-level=TRACE --storage-properties-on-edges=true --storage-snapshot-interval-sec=2 --storage-snapshot-retention-count=3 --storage-mode=ON_DISK_TRANSACTIONAL --storage-snapshot-on-exit=true"
    volumes:
      - mg_lib:/var/lib
      - mg_log:/var/log
      - mg_etc:/etc/memgraph
    deploy:
      resources:
        limits:
          cpus: '1'
          memory: 1G
volumes:
  mg_lib:
    driver: local
    driver_opts:
      type: 'none'
      o: 'bind'
      device: './memgraph/data'
  mg_log:
    driver: local
    driver_opts:
      type: 'none'
      o: 'bind'
      device: './memgraph/log'
  mg_etc:
    driver: local
    driver_opts:
      type: 'none'
      o: 'bind'
      device: './memgraph/config'

[vector-mj]

That's great to hear @vector-mj 😄 Btw., if you don't mind me asking, what are you working on with Memgraph?

Hi again @katarinasupe
I'm sorry to reply too late. I'm working on my personal social media project with many relations between users, and after some research, I decided to use Memgraph instead of Neo4j for faster queries.

[katarinasupe]

Glad to hear you decided to use Memgraph 😄 If you have more questions or you'd like to share more about the project with the community, join our Discord server.

[katarinasupe]

Hi @vector-mj, thank you for opening the issue. We are aware of the bind volumes not working as expected, probably due to file ownership issues. Is this a blocker for you currently or is the Docker volume workaround good enough for you for now?

[vector-mj]

Hi @vector-mj, thank you for opening the issue. We are aware of the bind volumes not working as expected, probably due to file ownership issues. Is this a blocker for you currently or is the Docker volume workaround good enough for you for now?

Hi @katarinasupe
I want to send my backups (snapshots) to S3 object storage, and with Docker volumes, I can't do this. Also, I tried to change the file ownership and permissions, but it didn't solve my issue. I think maybe it can be solved in Dockerfile..., Do you have any solution for this case?

[katarinasupe]

That's great to hear @vector-mj 😄 Btw., if you don't mind me asking, what are you working on with Memgraph?