omv-extras 6.3 / openmediavault-compose 6.7

Zitat von belierzz

I have installed latest update of docker-compose to version 6.9.3. Unfortunately the compose files are not installed in their respective folders within the folder defined in settings (called "dockercomp"), but in single folders, e.g. dockercompplex, dockercompadguardhome etc.

Anyone has the same issue and / or can point me in the direction how to solve?

I have a similar issue except for the compose files. i.e. composePlex instead of compose/Plex. When checking the file it fails because I assume the YAML files are in the wrong place.

I changed Compose folder to root:users, and everyone.

When I try and add container no files are saved to compose folder.

ssh'd into VM
cd to drive
ls -la
drwxr-xr-x  9 root root   4096 Jul  9 11:15 .
drwxr-xr-x  6 root root   4096 Jul  6 17:57 ..
drwxrwsrwx  2 root users  4096 Jul  6 17:58 appdata
-rw-------  1 root root   6144 Jul  6 18:10 aquota.group
-rw-------  1 root root   7168 Jul  6 18:10 aquota.user
drwxrwsrwx  4 root users  4096 Jul  9 11:21 compose
drwxrwxrwx  2 root users  4096 Jul  9 11:13 composecomposerize
drwxrwxrwx  2 root users  4096 Jul  9 11:13 composediun
drwxrwxrwx  2 root users  4096 Jul  9 11:15 composedozzle
drwx------  2 root root  16384 Jul  6 17:56 lost+found
drwxrwsrwx+ 4 root users  4096 Jul  6 18:00 media

compose was already there from other testing.

folder composeCONTAINER contains both yml files.

Below is when doing 'Check'

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/srv/dev-disk-by-uuid-791e0595-fd15-4e1c-a1fc-cc15d932ccbc/compose/diun/diun.yml' --env-file '/srv/dev-disk-by-uuid-791e0595-fd15-4e1c-a1fc-cc15d932ccbc/compose/diun/diun.env' config 2>&1': service "diun" refers to undefined volume CHANGE_TO_COMPOSE_DATA_PATH/diun: invalid compose project

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/srv/dev-disk-by-uuid-791e0595-fd15-4e1c-a1fc-cc15d932ccbc/compose/diun/diun.yml' --env-file '/srv/dev-disk-by-uuid-791e0595-fd15-4e1c-a1fc-cc15d932ccbc/compose/diun/diun.env' config 2>&1': service "diun" refers to undefined volume CHANGE_TO_COMPOSE_DATA_PATH/diun: invalid compose project in /usr/share/openmediavault/engined/rpc/compose.inc:566
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMVRpcServiceCompose->{closure}('/tmp/bgstatusrH...', '/tmp/bgoutputOP...')
#1 /usr/share/openmediavault/engined/rpc/compose.inc(569): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#2 [internal function]: OMVRpcServiceCompose->doCommand(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('doCommand', Array, Array)
#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Compose', 'doCommand', Array, Array, 1)
#6 {main}

What does the backup exactly backup? I searched the omv extras website but could not find a clear answer.

Is it only the compose shared folder? Or are the CHANGE_TO_COMPOSE_DATA_PATH and docker install directory also included?

I took a look at the script on github. Looks like a great feature to have!! Thank you!

Also I was a little skeptical in the beginning about the compose plugin since it was something new.

Now I really like it!! Also thank you for that!!

I just need to understand clearly what it does before I trust it. That is why I sometimes ask questions that maybe look stupid/simple.

Got to say that I think 'CHANGE_TO_COMPOSE_DATA_PATH' is the one of the best additions you've made to the plugin! Makes life so much easier when adding containers and using test OMV vm's (yes I have set 1 up). Great addition!!

Hi,

I saw that the network section has now Subnet, Gateway and IP range sections for macvlan, but it doesnt seem to be using the values that I put in it, here are my values:

but here is what I get from the inspect:

[
  {
    "Name": "netbr",
    "Id": "df46b4822e54ed49b09596e15a3436526232b381595772a96be4d32500c2be41",
    "Created": "2023-07-10T15:11:39.375777423+01:00",
    "Scope": "local",
    "Driver": "macvlan",
    "EnableIPv6": false,
    "IPAM": {
      "Driver": "default",
      "Options": {},
      "Config": [
        {
          "Subnet": "172.19.0.0/16",
          "Gateway": "172.19.0.1"
        }
      ]
    },
    "Internal": false,
    "Attachable": false,
    "Ingress": false,
    "ConfigFrom": {
      "Network": ""
    },
    "ConfigOnly": false,
    "Containers": {},
    "Options": {
      "parent": "br0"
    },
    "Labels": {}
  }
]

END OF LINE
█

I use this command to do the same thing:

docker network create -d macvlan \
    --subnet=192.168.0.0/24 \
    --gateway=192.168.0.1  \
    -o parent=br0 \
     netbr

which works. This might be a bug in the plugin.

Hi guys,

Need some help, my filesystem is 100%full - believe its related with the last version of compose plugin - cannot track the process responsible for filling up the mirror in RAID. I unmounted the md0 filesystem, cleared the browser cache, rebooted the machine, no luck.

Didn't found a similar case on the forum - (maybe I didn't searched better?) - need some help here - no way I have 6TB filled in one day.

gigi@debian:~$ df -H
Filesystem Size Used Avail Use% Mounted on
udev 1.5G 0 1.5G 0% /dev
tmpfs 385M 3.1M 382M 1% /run
/dev/mmcblk0p2 62G 4.1G 54G 7% /
tmpfs 2.0G 0 2.0G 0% /dev/shm
tmpfs 5.3M 4.1k 5.3M 1% /run/lock
tmpfs 2.0G 0 2.0G 0% /tmp
/dev/mmcblk0p1 495M 64M 406M 14% /boot
folder2ram 2.0G 872M 1.1G 46% /var/log
/dev/md0 6.0T 6.0T 291k 100% /srv/dev-disk-by-uuid-eff5c55e-5186-4381-9a02-9dc0334ab796
folder2ram 2.0G 0 2.0G 0% /var/tmp
folder2ram 2.0G 1.6M 2.0G 1% /var/lib/openmediavault/rrd
folder2ram 2.0G 975k 2.0G 1% /var/spool
folder2ram 2.0G 15M 2.0G 1% /var/lib/rrdcached
folder2ram 2.0G 4.1k 2.0G 1% /var/lib/monit
folder2ram 2.0G 1.7M 2.0G 1% /var/cache/samba
tmpfs 385M 0 385M 0% /run/user/1000

Zitat von ryecoaaron

How would the compose plugin do this? It doesn't add but a few text files to the filesystem. Your containers might have done this though. Did you try the system prune option?

Where is located that option? I only use the prune for docker.

Zitat von ryecoaaron

It is docker prune system. It is in the Files tab under the Prune menu.

Yeah, but what option - container or image give the same answer>

Total reclaimed space: 0B

END OF LINE

█

Zitat von ryecoaaron

It isn't adding the options because you aren't passing a gateway. I guess I will have to change the plugin to allow this.

you mean "IP Range"? Because in my screenshot I do have a gateway. I usually setup my IPs manually in the compose file, I do not want them to be dynamically allocated.

Zitat von ryecoaaron

If that doesn't free up space, look at [How-To] Fix full OS filesystem - GUI login loop

I already read that but my issues isn't the OS filesystem but the raid mounted filesystem if filling: