Can't start daemon docker.

    • OMV 3.x
    • Resolved
    • Can't start docker.

      I was looking at this thread. Someone needs to dumb it down for me. I"m a new linux and OMV user.
      Can't start DOCKER

      Docker was working last night. I pulled an emby image and created a container yesterday before shutting down the box. Today docker won't start back up.

      Source Code

      1. root@server:~# systemctl status docker
      2. ● docker.service - Docker Application Container Engine
      3. Loaded: loaded (/lib/systemd/system/docker.service; enabled)
      4. Drop-In: /etc/systemd/system/docker.service.d
      5. └─openmediavault.conf
      6. Active: failed (Result: start-limit) since Sun 2017-07-02 08:50:27 PDT; 3min 51s ago
      7. Docs:
      8. Process: 1024 ExecStart=/usr/bin/docker daemon -H fd:// $DOCKER_OPTS $OMVDOCKE R_API $OMVDOCKER_IMAGE_PATH (code=exited, status=1/FAILURE)
      9. Main PID: 1024 (code=exited, status=1/FAILURE)
      10. Jul 02 08:50:27 avocado systemd[1]: Unit docker.service entered failed state.
      11. Jul 02 08:50:27 avocado systemd[1]: docker.service holdoff time over, sched...t.
      12. Jul 02 08:50:27 avocado systemd[1]: Stopping Docker Application Container E.....
      13. Jul 02 08:50:27 avocado systemd[1]: Starting Docker Application Container E.....
      14. Jul 02 08:50:27 avocado systemd[1]: docker.service start request repeated t...t.
      15. Jul 02 08:50:27 avocado systemd[1]: Failed to start Docker Application Cont...e.
      16. Jul 02 08:50:27 avocado systemd[1]: Unit docker.service entered failed state.
      17. Hint: Some lines were ellipsized, use -l to show in full.
      Display All

      Source Code

      1. root@server:~# ps aux | grep docker
      2. root 1293 0.0 0.0 12732 2196 pts/0 S+ 08:55 0:00 grep docker


      Source Code

      1. # Docker Upstart and SysVinit configuration file
      2. #
      4. #
      5. # Please see the documentation for "systemd drop-ins":
      6. #
      7. #
      8. # Customize location of Docker binary (especially for development testing).
      9. #DOCKERD="/usr/local/bin/dockerd"
      10. # Use DOCKER_OPTS to modify the daemon startup options.
      11. #DOCKER_OPTS="--dns --dns"
      12. # If you need Docker to use an HTTP proxy, it can also be specified here.
      13. #export http_proxy=""
      14. # This is also a handy place to tweak where Docker's temporary files go.
      15. #export DOCKER_TMPDIR="/mnt/bigdrive/docker-tmp"
      16. ### Do not change these lines. They are added and updated by the OMV Docker GUI plugin.
      17. OMVDOCKER_API="-H tcp://"
      19. ### Do not add any configuration below this line. It will be removed when the plugin is removed
      Display All

      Help please.
    • Purging the docker-engine package. Deleting the left over folders before reinstalling seem to do the trick. The daemon docker successfully restarts even after rebooting. Though I did also create a user to attach to the emby container. On the first round my OMV had no users.

      I still have an error when attempting to use the docker GUI plugin with the result of it being unusable. I negated the issue by using CLI.

      Error #0:exception 'OMVModuleDockerException' with message 'Error: "Failed to connect to localhost port 42005: Connection refused" - Code: 7' in /usr/share/omvdocker/Utils.php:73Stack trace:#0 /usr/share/omvdocker/Utils.php(167): OMVModuleDockerUtil::doApiCall('http://localhos...')#1 /usr/share/openmediavault/engined/rpc/ OMVModuleDockerUtil::getImageList(42005, true)#2 [internal function]: OMVRpcServiceDocker->getImages(Array, Array)#3 /usr/share/php/openmediavault/rpc/ call_user_func_array(Array, Array)#4 /usr/share/php/openmediavault/rpc/ OMV\Rpc\ServiceAbstract->callMethod('getImages', Array, Array)#5 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Docker', 'getImages', Array, Array, 1)#6 {main}
    • Users Online 1

      1 Guest