rajangoswamiTWS
commented
2 days ago Same here. Suddenly started getting same error on Ubuntu VM. We had r2r instance up and running fine for last few days, and after VM OS got updated, unable to run r2r containers due to this error since then.
wondering if this is related to https://github.com/docker/compose/issues/12139?
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior: cd r2r r2r serve --docker --config-name=local_llm --exclude-ollama=False
I think I may be at the final hurdle, probably somthing simple I'm missing, please see the error I am now receiving:
[+] Running 14/10 ✔ Network r2r-network Created 0.1s ✔ Container r2r-hatchet-dashboard-1 Created 0.5s ✔ Container r2r-ollama-1 Created 0.5s ✔ Container r2r-traefik-1 Created 0.5s ✔ Container r2r-neo4j-1 Created 0.5s ✔ Container r2r-unstructured-1 Created 0.5s ✔ Container r2r-postgres-1 Created 0.5s ✔ Container r2r-r2r-dashboard-1 Created 0.5s ✔ Container r2r-hatchet-rabbitmq-1 Created 0.5s ✔ Container r2r-hatchet-migration-1 Created 0.0s ✔ Container r2r-hatchet-setup-config-1 Created 0.0s ✔ Container r2r-setup-token-1 Created 0.0s ✔ Container r2r-hatchet-engine-1 Created 0.0s ✔ Container r2r-hatchet-api-1 Created 0.0s ⠋ Container r2r-r2r-1 Creating 0.0s Error response from daemon: invalid mount config: must use either propagation mode "rslave" or "rshared" when mount source is within the daemon root, daemon root: "/var/lib/docker", bind mount source: "/", propagation: "rprivate" Waiting for all services to become healthy... Error checking health of r2r
I am running compose from cloned r2r folder and so I don't get why I have this issue.
Expected behavior Containers run
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information): ubuntu 24.04