compose plugin - help needed for settings

frankfurt · Jan 3rd 2026

I installed the compose plugin 8.1.1 – OK.

In the compose settings, I see under docker info installed and running.

I created and assigned shared folders for compose files, data and backup. For docker storage, I left /var/lib/docker.

Then I clicked on save. When I try to apply the changes, I get the following error message.

I don't understand this message and what is going wrong here.

Thank you for your help.

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color compose 2>&1' with exit code '1': raspi5:
----------
          ID: configure_compose_global_env_file
    Function: file.managed
        Name: /srv/dev-disk-by-uuid-BA923A77923A3869/appdata/global.env
      Result: False
     Comment: Failed to change mode to 0600
     Started: 21:59:20.177098
    Duration: 7.767 ms
     Changes:
----------
          ID: container_storage_dir
    Function: file.directory
        Name: /var/lib/docker
      Result: True
     Comment: The directory /var/lib/docker is in the correct state
     Started: 21:59:20.184999
    Duration: 0.958 ms
     Changes:
----------
          ID: docker_install_packages
    Function: pkg.installed
      Result: True
     Comment: All specified packages are already installed
     Started: 21:59:20.989547
    Duration: 34.535 ms
     Changes:
----------
          ID: configure_etc_docker_dir
    Function: file.directory
        Name: /etc/docker
      Result: True
     Comment: The directory /etc/docker is in the correct state
     Started: 21:59:21.024233
    Duration: 1.017 ms
     Changes:
----------
          ID: /etc/docker/daemon.json
    Function: file.serialize
      Result: True
     Comment: File /etc/docker/daemon.json is in the correct state
     Started: 21:59:21.025356
    Duration: 2.791 ms
     Changes:
----------
          ID: docker
    Function: service.running
      Result: True
     Comment: The service docker is already running
     Started: 21:59:21.029297
    Duration: 45.932 ms
     Changes:
----------
          ID: common_install_packages
    Function: pkg.installed
      Result: True
     Comment: All specified packages are already installed
     Started: 21:59:21.075708
    Duration: 9.799 ms
     Changes:
----------
          ID: /etc/systemd/system/docker.service.d/waitAllMounts.conf
    Function: file.managed
      Result: True
     Comment: File /etc/systemd/system/docker.service.d/waitAllMounts.conf is in the correct state
     Started: 21:59:21.085651
    Duration: 2.067 ms
     Changes:
----------
          ID: systemd_daemon_reload
    Function: cmd.run
        Name: systemctl daemon-reload
      Result: True
     Comment: State was not run because none of the onchanges reqs changed
     Started: 21:59:21.088973
    Duration: 0.004 ms
     Changes:
----------
          ID: configure_compose_scheduled_backup
    Function: file.managed
        Name: /etc/cron.d/omv-compose-backup
      Result: True
     Comment: File /etc/cron.d/omv-compose-backup is in the correct state
     Started: 21:59:21.089048
    Duration: 11.955 ms
     Changes:
----------
          ID: configure_compose_scheduled_update
    Function: file.managed
        Name: /etc/cron.d/omv-compose-update
      Result: True
     Comment: File /etc/cron.d/omv-compose-update is in the correct state
     Started: 21:59:21.101148
    Duration: 11.296 ms
     Changes:
----------
          ID: configure_compose_scheduled_prune
    Function: file.managed
        Name: /etc/cron.d/omv-compose-prune
      Result: True
     Comment: File /etc/cron.d/omv-compose-prune is in the correct state
     Started: 21:59:21.112587
    Duration: 11.263 ms
     Changes:
----------
          ID: configure_compose_scheduled_start
    Function: file.managed
        Name: /etc/cron.d/omv-compose-start
      Result: True
     Comment: File /etc/cron.d/omv-compose-start is in the correct state
     Started: 21:59:21.123991
    Duration: 11.189 ms
     Changes:
----------
          ID: configure_compose_scheduled_build
    Function: file.managed
        Name: /etc/cron.d/omv-compose-build
      Result: True
     Comment: File /etc/cron.d/omv-compose-build is in the correct state
     Started: 21:59:21.135323
    Duration: 12.23 ms
     Changes:
----------
          ID: configure_compose_scheduled_stop
    Function: file.managed
        Name: /etc/cron.d/omv-compose-stop
      Result: True
     Comment: File /etc/cron.d/omv-compose-stop is in the correct state
     Started: 21:59:21.147698
    Duration: 11.239 ms
     Changes:

Summary for raspi5
-------------
Succeeded: 14
Failed:     1
-------------
Total states run:     15
Total run time:  174.042 ms
[ERROR   ] Failed to change mode to 0600

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color compose 2>&1' with exit code '1': raspi5:
----------
          ID: configure_compose_global_env_file
    Function: file.managed
        Name: /srv/dev-disk-by-uuid-BA923A77923A3869/appdata/global.env
      Result: False
     Comment: Failed to change mode to 0600
     Started: 21:59:20.177098
    Duration: 7.767 ms
     Changes:
----------
          ID: container_storage_dir
    Function: file.directory
        Name: /var/lib/docker
      Result: True
     Comment: The directory /var/lib/docker is in the correct state
     Started: 21:59:20.184999
    Duration: 0.958 ms
     Changes:
----------
          ID: docker_install_packages
    Function: pkg.installed
      Result: True
     Comment: All specified packages are already installed
     Started: 21:59:20.989547
    Duration: 34.535 ms
     Changes:
----------
          ID: configure_etc_docker_dir
    Function: file.directory
        Name: /etc/docker
      Result: True
     Comment: The directory /etc/docker is in the correct state
     Started: 21:59:21.024233
    Duration: 1.017 ms
     Changes:
----------
          ID: /etc/docker/daemon.json
    Function: file.serialize
      Result: True
     Comment: File /etc/docker/daemon.json is in the correct state
     Started: 21:59:21.025356
    Duration: 2.791 ms
     Changes:
----------
          ID: docker
    Function: service.running
      Result: True
     Comment: The service docker is already running
     Started: 21:59:21.029297
    Duration: 45.932 ms
     Changes:
----------
          ID: common_install_packages
    Function: pkg.installed
      Result: True
     Comment: All specified packages are already installed
     Started: 21:59:21.075708
    Duration: 9.799 ms
     Changes:
----------
          ID: /etc/systemd/system/docker.service.d/waitAllMounts.conf
    Function: file.managed
      Result: True
     Comment: File /etc/systemd/system/docker.service.d/waitAllMounts.conf is in the correct state
     Started: 21:59:21.085651
    Duration: 2.067 ms
     Changes:
----------
          ID: systemd_daemon_reload
    Function: cmd.run
        Name: systemctl daemon-reload
      Result: True
     Comment: State was not run because none of the onchanges reqs changed
     Started: 21:59:21.088973
    Duration: 0.004 ms
     Changes:
----------
          ID: configure_compose_scheduled_backup
    Function: file.managed
        Name: /etc/cron.d/omv-compose-backup
      Result: True
     Comment: File /etc/cron.d/omv-compose-backup is in the correct state
     Started: 21:59:21.089048
    Duration: 11.955 ms
     Changes:
----------
          ID: configure_compose_scheduled_update
    Function: file.managed
        Name: /etc/cron.d/omv-compose-update
      Result: True
     Comment: File /etc/cron.d/omv-compose-update is in the correct state
     Started: 21:59:21.101148
    Duration: 11.296 ms
     Changes:
----------
          ID: configure_compose_scheduled_prune
    Function: file.managed
        Name: /etc/cron.d/omv-compose-prune
      Result: True
     Comment: File /etc/cron.d/omv-compose-prune is in the correct state
     Started: 21:59:21.112587
    Duration: 11.263 ms
     Changes:
----------
          ID: configure_compose_scheduled_start
    Function: file.managed
        Name: /etc/cron.d/omv-compose-start
      Result: True
     Comment: File /etc/cron.d/omv-compose-start is in the correct state
     Started: 21:59:21.123991
    Duration: 11.189 ms
     Changes:
----------
          ID: configure_compose_scheduled_build
    Function: file.managed
        Name: /etc/cron.d/omv-compose-build
      Result: True
     Comment: File /etc/cron.d/omv-compose-build is in the correct state
     Started: 21:59:21.135323
    Duration: 12.23 ms
     Changes:
----------
          ID: configure_compose_scheduled_stop
    Function: file.managed
        Name: /etc/cron.d/omv-compose-stop
      Result: True
     Comment: File /etc/cron.d/omv-compose-stop is in the correct state
     Started: 21:59:21.147698
    Duration: 11.239 ms
     Changes:

Summary for raspi5
-------------
Succeeded: 14
Failed:     1
-------------
Total states run:     15
Total run time:  174.042 ms
[ERROR   ] Failed to change mode to 0600 in /usr/share/php/openmediavault/system/process.inc:247
Stack trace:

Display More

BernH · Jan 3rd 2026

Code

          ID: configure_compose_global_env_file
    Function: file.managed
        Name: /srv/dev-disk-by-uuid-BA923A77923A3869/appdata/global.env
      Result: False
     Comment: Failed to change mode to 0600
     Started: 21:59:20.177098
    Duration: 7.767 ms
     Changes:
----------

based on this section of your error, the problem seems to be with the global.env file.

Does the file exist at the path specified?

***edit***

also based on the uuid, this is not a linux filesystem.

That is likely the root of the problem.

Docker requires a filesystem that handles linux permissions and ownership.

frankfurt · Jan 4th 2026

Quote from BernH

also based on the uuid, this is not a linux filesystem.

That is likely the root of the problem.

Docker requires a filesystem that handles linux permissions and ownership.

OK..the hdd is wih ntfs(windows) mounted...so I start over again..

Thx and i will return here

BernH · Jan 4th 2026

Quote from frankfurt

OK..the hdd is wih ntfs(windows) mounted...so I start over again..
Thx and i will return here

While linux can read/write an ntfs drive, an ntfs drive is a windows format, not a linux format. Any storage that is supposed to be permanently used on the server should be in a linux format. ntfs can be used as a temporary drive to copy to/from the linux drives.

frankfurt · Jan 4th 2026

Thanks again.

I was able to configure the settings with an ext4 formatted hdd.

Next, I would like to install Audiobookshelf.

Let's see if I can manage that.

BernH · Jan 4th 2026

You're welcome.

Now that you have a working docker you should be able to.

I would recommend that you change the default docker storage path from /var/lib/docker to a directory on a data drive though. leaving it at the default /var/lib/docker means it is on the OS drive. If your os needs to be reinstalled, you will loose all the docker containers and if your os drive is small, you could fill it to the point of breaking omv.

Having it on a data drive means that in the event of an os re-install, just setting the paths for storage and appdata again will get everything working without having to do any rebuilds.

compose plugin - help needed for settings

macom Jan 4th 2026

Participate now!