Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rancher Desktop Deployment #1293

Open
jonosooty opened this issue Oct 1, 2024 · 5 comments
Open

Rancher Desktop Deployment #1293

jonosooty opened this issue Oct 1, 2024 · 5 comments

Comments

@jonosooty
Copy link

Hi,
I would like to setup on Mac m1 , but I need to use rancher desktop due to company requirements.
I guess there is some difference in the volume mappings between docker desktop and rancher desktop.

Do you know if it should be possible to change the config to address the error I get. Sorry for the novice tech. questions , I am a PO.

✔ Container r2r-hatchet-setup-config-1 Created 0.0s
✔ Container r2r-hatchet-api-1 Created 0.0s
✔ Container r2r-setup-token-1 Created 0.0s
⠋ Container r2r-r2r-1 Creating 0.1s
✔ Container r2r-hatchet-engine-1 Created 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
..... never becomes healthy....

If I inspect the volumes I get.

{
    "CreatedAt": "2024-10-01T14:09:01+02:00",
    "Driver": "local",
    "Labels": {
        "com.docker.compose.project": "r2r",
        "com.docker.compose.version": "2.29.5",
        "com.docker.compose.volume": "postgres_data"
    },
    "Mountpoint": "/var/lib/docker/volumes/r2r_postgres_data/_data",
    "Name": "r2r_postgres_data",
    "Options": null,
    "Scope": "local"
}

]

Many Thanks for any insights.
Jono

@NolanTrem
Copy link
Collaborator

Hey @jonosooty, we're about to push out a version that you can run locally much easier. There's also a much simpler Docker that may not throw this, but as is (R2R release 3.1.X) this will be hard to diagnose.

Let me know if you're able to get running with R2R version 3.2—I have a feeling it'll be a much smoother start!

@jonosooty
Copy link
Author

Thanks so much for the quick reply. I will give 3.2 a go.
Jono

@jonosooty
Copy link
Author

Hi,

Thanks I tried 3.2 but I had the same problems.

  1. TRYING TO MOUNT ROOT /

It is trying to mount / as the CONFIG_PATH environment variable is not set. Excuse the basic question, to where should CONFIG_PATHH be set or where are the default config files that should be there?

...
volumes:
- ${CONFIG_PATH:-/}:${CONFIG_PATH:-/app/config}
...

  1. PROPOGATE
    I guess I need to set the volume bind propagation to something like
    propagation: rshared. for all volumes.

Thanks for your help,
Jono

@NolanTrem
Copy link
Collaborator

Any chance you're able to run outside of Docker? Running r2r serve alone is possible now.

@jonosooty
Copy link
Author

Thanks, I will try that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants