Setup not showing all partitions

Trying to use the http://ip:8089 setup interface (using docker compose). #2 storage, does not list all my partitions (non-system, top level partitions e.g. /local). Permissions are more generous (775) than system partitions and not owned by root. I want all the channel-dvr created data, configs, etc. in this partition. My docker-compose.yml is in /local and volumes are defined as:

volumes:
      - ./config:/channels-dvr
      - ./recordings:/shares/DVR

How do I point the setup to the desired location?
Thanks!

Have you tried using absolute paths like this

volumes:
  - /local/config:/channels-dvr
  - /local/recordings:/shares/DVR

This should also work

volumes:
  - /local/config:/channels-dvr
  - /local/recordings:/local/recordings

Which OS and docker are you using?

Thank you for the response. Ubuntu 24.04, docker 29.5.2.
The issue wasn't absolute vs relative, it was how the info was displayed. Selecting channels-dvr made the selected path look like:
/channels-dvr (which to me looked like a root level directory as the other paths displayed were all from the top root directory). I was leery to select that as I've had other docker images put things in /var and other places which over time filled the root partition making a mess. Personally I think displaying the whole selected path would be less confusing.

That's the directory within the container that Channels DVR uses to store executables, logs and other things. You should never changes that directory to the right of the colon (:) in the volume mapping.

The other volume you showed as /shares/DVR is the directory within the container that Channels DVR records to and you map it to your host using the volumes: This directory you select in setup, so it can be anything inside the container, but must be mapped to the host directory you want recordings to go in.

For docker directories and ports, the value to the left of the colon (:) is the host OS directory or port and to the right of the colon (:) is the one inside the container.

Channels DVR running in a container can only use ports and directories inside the container. That's why you need to map those to ports and directories on your host OS.

Another important thing to remember is that Channels DVR runs on top of Linux in the container and Linux uses cAsE sEnSiTiVe directory and file names.
So if you map the volume Channels DVR records to as /shares/DVR

volumes:
  - /local/config:/channels-dvr
  - /local/recordings:/shares/DVR

But in Channels DVR setup you select the directory /shares/dvr
Your recordings will be stored in the container instead of in your host directory /local/recordings
Never guess how I know that :blush:

Although I know that very well having used Linux a long time, it is good to have that as part of the answers here as I'm sure many folks could get burned by that. Thanks for adding that to the thread!

1 Like

I did

Where are my recordings