https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
f
It is hard to say without further information. Like are you running on plain docker, or on Kubernetes? What is the command to start your container? Is the data directory a bind-mount to the host, or a separate volume?
r
It’s running on docker, using 
docker compose up
. My docker cli is symlinked to rancher: 
/.docker/cli-plugins/docker-compose -> /.rd/bin/docker-compose
Compose handled the creation and start of the container. I’m not entirely sure how to check the last question you asked, but I didn’t do any special directory binding. So whatever is out-of-the-box is what I’m using
f
It will depend on your compose YAML file.
r
Here’s the volumes section of the YAML. I should note that this is the same exact YAML I used with docker desktop:
Copy code
volumes:
      - ${VOLUMES_ROOT}/postgres/data:/var/lib/postgresql/data:delegated
Did I provide all the info you needed to look into this?
f
Not really; realistically I would need a repro case that I can run and see the error myself. If I have to figure out myself how to reproduce the issue, then I probably won't find the time to squeeze it in.
I understand that you may not be able to post your actual compose file, but you should be able to condense it down to a minimal config that reproduces the issue. Then it would be best to attach it as a Github issue, so it can be tracked properly instead of getting lost in the Slack thread history
r
f
Thank you!
r
I was taking a look thru the issue in rancher desktop and found this. I believe this is exactly the issue I’m having https://github.com/rancher-sandbox/rancher-desktop/issues/1209
Turns out volume mounting with 
docker compose
in both Docker and Rancher Desktop has some issues. I followed the instructions in the comment in the above issue thread: https://github.com/rancher-sandbox/rancher-desktop/issues/1209#issuecomment-1370181132 After adding the override config, I restarted rancher: 
rdctl shutdown
, then 
rdctl start
(you may have to reset the context back to rancher desktop: 
docker context use rancher-desktop
) I ran 
docker compose up
and all my containers seemed to be running with the right permissions except for my postgres one. So I just manually ran it without using compose and it worked: 
docker run --name postgres11 -e POSTGRES_USER=$PG_USER -e POSTGRES_PASSWORD=$PG_PASS -p 5432:5432 --detach postgres:11
f
Thanks! Can you please keep your Github issue updated with your latest findings?
r
Just did
f
Thanks, just got the notification after I pressed Enter. 😄
✅ 1
Open in Slack
PreviousNext
Powered by