Dockge compose file questions?

Good afternoon everyone

I have a question that needs answering in regards to Dockge and i’m a little confused on mount points and configurations for each individual app and dockge as a whole.

So i migrated all of my apps from using Truecharts over to a debian 12 machine under proxmox running Dockge. Everything was set up and after diving into YouTube videos, docker hub etc i got all my apps running under Dockge with compose files, pointed to mount points and so fourth and it’s been running fine since.

After upgrading Truenas Scale to the latest EE i have noticed Dockge is available in Truenas as an app so looking to get into testing it on Truenas. I am having a problem with mount points and loading my first compose file. I have installed Dockge and under installation i have both the stack and data storage pointing towards a new created host path of.

/mnt/Vol1/Docker/Dockge/Stacks
/mnt/Vol1/Docker/Dockge/Data

I have also added addition storage of

/mnt/Vol1/Audio
/mnt/Vol1/Program_Data

All datasets created have been given correct permissions for the apps to get read/write access so Dockge can do it’s thing.

Dockge is currently running fine and when i open the console in Dockge i can see both Audio & Program_Data datasets that are mounted in Dockge and can navigate through them all. The problem i am now facing is mounts in compose files.

So under the Program_Data dataset in Truenas i created a dataset called Jellyfin where the Jellyfin configurations, users and so fourth will live and Dockge can access it. When i go to load the following compose file though in Dockge.

services:
jellyfin:
image: jellyfin/jellyfin
container_name: jellyfin
user: 1000:1000
network_mode: host
volumes:
- /Program_Data/Dockge/Stacks/Jellyfin/config:/config
- /Program_Data/Dockge/Stacks/Jellyfin/cache:/cache
- type: bind
source: /Audio
target: /Music
read_only: true
restart: unless-stopped
networks: {}

I am greeted with the following error

Error response from daemon: invalid mount config for type “bind”: bind source path does not exist: /Audio

I tried changing the compose to /mnt/Vol1/Audio and the Program_Data to the same and it’s just stuck in an endless reboot cycle. Am i doing the compose file wrong in terms of mounting any datasets or do i have the Dockge set up wrong?

Thanks

Hi!

This seems correct to me (not /Audio) but i would check if

Is the right user.

Or you can try to mount your files with a volume instead of a bind (yeah, bind are surely better for that, but as last chance…)

There is no reason to do this.

You need to add the mounts to the actual stacks your create/manage with Dockge, not to Dockge itself.

This video may help understanding things

Thank you everyone and for the video link i solved it, for anyone interested in learning how, i did the following.

1 - Created a Dataset called Docker in Truenas webgui under Vol1 and gave it the right permissions

2 - Under the Docker dataset i created 2 datasets Dockge & Program_Data and gave it the right permissions

3 - Under Dockge i created 2 datasets both Data & Stacks and under Program_Data i created a dataset Jellyfin and gave it the right permissions

4 - In the Truenas webgui i installed Dockge from apps and using hostpath i pointed Data & Stacks to the relevant datasets and then saved the config and left it installing.

5 - Once Dockge had installed and was running i jumped to Dockge webgui

6 - I got a username and password created then set up my first stack which is Jellyfin

7 - When creating a stack, for the volumes i used /mnt/Vol1/Docker/Program_Data/Jellyfin

8 - For the media to be seen i used source: /mnt/Vol1/Audio mounted at /Audio

This is where i hit a brick wall and it kept restarting till i realised the UID may be the culprit. I then added user: 0:0 to the compose file just to see if it would install and run using root UID and it installed fine (ill change the UID asap) and then when jumping to the webgui i was greeted with the Jellyfin web wizard.

My next step is to created a few more datasets under Program_Data for additional apps and get some more compose files running and tested.

Thanks again

1 Like