Docker not starting (error 500) after updating to OMW 6.9.16-1

  • OMW 6.9.16-1 (Shaitan)

    Kernel : Linux 6.1.21-v8+


    Hi everyone,


    my OMV 6 on a Raspberry 4 (with docker & portainer) was running well.

    After one year not starting the system, I did, and updated the system from the OMV web interface.

    After restarting the Raspberry, OMV works fine but Docker doesn't start.

    I tried to "Reinstall docker" from Services/Compose/Parameters button : process went ok to the "end of line"

    But when I click on "Restart Docker", I get this error :



    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=; systemctl restart 'docker' 2>&1' with exit code '1': Job for docker.service failed because the control process exited with error code.

    See "systemctl status docker.service" and "journalctl -xe" for details.


    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=; systemctl restart 'docker' 2>&1' with exit code '1': Job for docker.service failed because the control process exited with error code.

    See "systemctl status docker.service" and "journalctl -xe" for details. in /usr/share/php/openmediavault/system/process.inc:242

    Stack trace:

    #0 /usr/share/php/openmediavault/system/systemctl.inc(86): OMV\System\Process->execute(Array, 1)

    #1 /usr/share/php/openmediavault/system/systemctl.inc(150): OMV\System\SystemCtl->exec('restart', NULL, false)

    #2 /usr/share/openmediavault/engined/rpc/compose.inc(263): OMV\System\SystemCtl->restart()

    #3 [internal function]: OMVRpcServiceCompose->restartDocker(NULL, Array)

    #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

    #5 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('restartDocker', NULL, Array)

    #6 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Compose', 'restartDocker', NULL, Array, 1)

    #7 {main}



    I checked the shared folders for compose plugin and docker , they still exist on the HDD.


    Could someone help me?


    Thank you.

  • crashtest

    Approved the thread.
  • Thanks for the link.
    I tried to reach my containers through their IP (as said in the link), but none of them are working. I am not sure my problem is the same.
    I struggle for hours on this problem.
    Would upgrade to OMV 7 solve my problem?
    Is that a complicated task updating while not breaking all that is already working?

  • Here is the result of systemctl status docker.service :


    ● docker.service - Docker Application Container Engine

    Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset>

    Drop-In: /etc/systemd/system/docker.service.d

    └─waitAllMounts.conf

    Active: failed (Result: exit-code) since Mon 2025-02-17 18:49:23 CET; 18mi>

    TriggeredBy: ● docker.socket

    Docs: https://docs.docker.com

    Process: 1798 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/contain>

    Main PID: 1798 (code=exited, status=2)

    CPU: 389ms

  • Ok, I decided to upgrade version 6->7 , using command omv-release-upgrade.
    Installation went well, but when I push "apply pending changes", i get this error :

    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': pimachine:

    ----------

    ID: configure_compose_global_env_file

    Function: file.managed

    Name: /srv/dev-disk-by-uuid-9b701f30-caf2-4f7e-bcf2-bb430dd5d321/Compose/global.env

    Result: True

    Comment: File /srv/dev-disk-by-uuid-9b701f30-caf2-4f7e-bcf2-bb430dd5d321/Compose/global.env is in the correct state

    Started: 22:44:41.167044

    Duration: 491.437 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: 22:44:41.659032

    Duration: 481.866 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: 22:44:42.141423

    Duration: 519.282 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: 22:44:42.661129

    Duration: 483.073 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: 22:44:43.144636

    Duration: 3.79 ms

    Changes:

    ----------

    ID: /etc/docker/daemon.json

    Function: file.serialize

    Result: True

    Comment: File /etc/docker/daemon.json is in the correct state

    Started: 22:44:43.148839

    Duration: 167.299 ms

    Changes:

    ----------

    ID: docker_install_packages

    Function: pkg.installed

    Result: True

    Comment: All specified packages are already installed and are at the desired version

    Started: 22:44:47.015228

    Duration: 196.629 ms

    Changes:

    ----------

    ID: docker_compose_install_packages

    Function: pkg.installed

    Result: True

    Comment: All specified packages are already installed and are at the desired version

    Started: 22:44:47.212451

    Duration: 331.893 ms

    Changes:

    ----------

    ID: docker_purged_packages

    Function: pkg.purged

    Result: True

    Comment: None of the targeted packages are installed or partially installed

    Started: 22:44:47.544742

    Duration: 3.768 ms

    Changes:

    ----------

    ID: docker

    Function: service.running

    Result: False

    Comment: Job for docker.service failed because the control process exited with error code.

    See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.

    Started: 22:44:47.552352

    Duration: 777.069 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: 22:44:48.329861

    Duration: 241.792 ms

    Changes:

    ----------

    ID: systemd_daemon_reload_docker

    Function: cmd.run

    Name: systemctl daemon-reload

    Result: True

    Comment: State was not run because none of the onchanges reqs changed

    Started: 22:44:48.575511

    Duration: 0.022 ms

    Changes:

    ----------

    ID: create_usr_local_bin_dir

    Function: file.directory

    Name: /usr/local/bin

    Result: True

    Comment: The directory /usr/local/bin is in the correct state

    Started: 22:44:48.575861

    Duration: 4.14 ms

    Changes:


    Summary for pinasclem

    -------------

    Succeeded: 12

    Failed: 1

    -------------

    Total states run: 13

    Total run time: 3.702 s

    [ERROR ] Command '/bin/systemd-run' failed with return code: 1

    [ERROR ] stderr: Running scope as unit: run-r6097bb475f214fe3962a810b9680fe07.scope

    Job for docker.service failed because the control process exited with error code.

    See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.

    [ERROR ] retcode: 1

    [ERROR ] Job for docker.service failed because the control process exited with error code.

    See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.


    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': pinasclem:

    ----------

    ID: configure_compose_global_env_file

    Function: file.managed

    Name: /srv/dev-disk-by-uuid-9b701f30-caf2-4f7e-bcf2-bb430dd5d321/Compose/global.env

    Result: True

    Comment: File /srv/dev-disk-by-uuid-9b701f30-caf2-4f7e-bcf2-bb430dd5d321/Compose/global.env is in the correct state

    Started: 22:44:41.167044

    Duration: 491.437 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: 22:44:41.659032

    Duration: 481.866 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: 22:44:42.141423

    Duration: 519.282 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: 22:44:42.661129

    Duration: 483.073 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: 22:44:43.144636

    Duration: 3.79 ms

    Changes:

    ----------

    ID: /etc/docker/daemon.json

    Function: file.serialize

    Result: True

    Comment: File /etc/docker/daemon.json is in the correct state

    Started: 22:44:43.148839

    Duration: 167.299 ms

    Changes:

    ----------

    ID: docker_install_packages

    Function: pkg.installed

    Result: True

    Comment: All specified packages are already installed and are at the desired version

    Started: 22:44:47.015228

    Duration: 196.629 ms

    Changes:

    ----------

    ID: docker_compose_install_packages

    Function: pkg.installed

    Result: True

    Comment: All specified packages are already installed and are at the desired version

    Started: 22:44:47.212451

    Duration: 331.893 ms

    Changes:

    ----------

    ID: docker_purged_packages

    Function: pkg.purged

    Result: True

    Comment: None of the targeted packages are installed or partially installed

    Started: 22:44:47.544742

    Duration: 3.768 ms

    Changes:

    ----------

    ID: docker

    Function: service.running

    Result: False

    Comment: Job for docker.service failed because the control process exited with error code.

    See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.

    Started: 22:44:47.552352

    Duration: 777.069 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: 22:44:48.329861

    Duration: 241.792 ms

    Changes:

    ----------

    ID: systemd_daemon_reload_docker

    Function: cmd.run

    Name: systemctl daemon-reload

    Result: True

    Comment: State was not run because none of the onchanges reqs changed

    Started: 22:44:48.575511

    Duration: 0.022 ms

    Changes:

    ----------

    ID: create_usr_local_bin_dir

    Function: file.directory

    Name: /usr/local/bin

    Result: True

    Comment: The directory /usr/local/bin is in the correct state

    Started: 22:44:48.575861

    Duration: 4.14 ms

    Changes:


    Summary for pinasclem

    -------------

    Succeeded: 12

    Failed: 1

    -------------

    Total states run: 13

    Total run time: 3.702 s

    [ERROR ] Command '/bin/systemd-run' failed with return code: 1

    [ERROR ] stderr: Running scope as unit: run-r6097bb475f214fe3962a810b9680fe07.scope

    Job for docker.service failed because the control process exited with error code.

    See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.

    [ERROR ] retcode: 1

    [ERROR ] Job for docker.service failed because the control process exited with error code.

    See "systemctl status docker.service" and "journalctl -xeu docker.service" for details. in /usr/share/php/openmediavault/system/process.inc:247

    Stack trace:

    #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()

    #1 /usr/share/openmediavault/engined/rpc/config.inc(187): OMV\Engine\Module\ServiceAbstract->deploy()

    #2 [internal function]: Engined\Rpc\Config->applyChanges()

    #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array()

    #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(155): OMV\Rpc\ServiceAbstract->callMethod()

    #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(628): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}()

    #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(152): OMV\Rpc\ServiceAbstract->execBgProc()

    #7 /usr/share/openmediavault/engined/rpc/config.inc(208): OMV\Rpc\ServiceAbstract->callMethodBg()

    #8 [internal function]: Engined\Rpc\Config->applyChangesBg()

    #9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array()

    #10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()

    #11 /usr/sbin/omv-engined(544): OMV\Rpc\Rpc::call()

    #12 {main}

  • See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.

    You could start by posting what it asks.


    And use CODE boxes for the outputs:

    [How-To] Post content in a code box - Guides - openmediavault

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!