Posts by anderbytes

    OMV uses whatever package Debian is using. If you are on OMV 2.x, it uses nut 2.6.4. If you are on OMV 3.x, it uses nut 2.7.2. Latest stable on the nut website is 2.7.4. That said, sometimes fixes are backported. So, you can't always go by version.

    Okay thanks for the info. I'll keep looking for the cause of the issue.

    Is NUT updated to lastest stable? Because I'm having trouble with my connection and need it updated to know if that resolve the issue.


    What Kernel are you on?

    Great! do you have a link for a good tutorial please

    There's no secret involved. The steps are same of the devicemapper tuturial, but use "overlay" instead of "devicemapper" in DOCKER_OPTS


    Before doing it... I backed up all my images with the "docker save" command (to load them later) and wrote down all my configs of containers, that I had to recreate later.

    I tested docker with 4.8 kernel, seems working well, what crash? any logs?

    I tracked down the issue to the following error:


    root@SRV{/var/log}: systemctl -l status docker.service
    docker.service - Docker Application Container Engine
    Loaded: loaded (/lib/systemd/system/docker.service; enabled)
    Drop-In: /etc/systemd/system/docker.service.d
    +-openmediavault.conf
    Active: failed (Result: exit-code) since Tue 2017-01-03 12:40:03 BRST; 6min ago
    Docs: https://docs.docker.com
    Process: 1183 ExecStart=/usr/bin/docker daemon -H fd:// $DOCKER_OPTS $OMVDOCKER_API $OMVDOCKER_IMAGE_PATH (code=exited, status=1/FAILURE)
    Main PID: 1183 (code=exited, status=1/FAILURE)



    Jan 03 12:40:02 SRV docker[1183]: time="2017-01-03T12:40:02.688499871-02:00" level=warning msg="[!] DON'T BIND ON ANY IP ADDRESS WITHOUT setting -tlsverify IF YOU DON'T KNOW WHAT YOU'RE DOING [!]"
    Jan 03 12:40:02 SRV docker[1183]: time="2017-01-03T12:40:02.692333359-02:00" level=info msg="libcontainerd: new containerd process, pid: 1326"
    Jan 03 12:40:03 SRV docker[1183]: time="2017-01-03T12:40:03.712906769-02:00" level=error msg="[graphdriver] prior storage driver \"aufs\" failed: driver not supported"
    Jan 03 12:40:03 SRV docker[1183]: time="2017-01-03T12:40:03.712961967-02:00" level=fatal msg="Error starting daemon: error initializing graphdriver: driver not supported"
    Jan 03 12:40:03 SRV systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
    Jan 03 12:40:03 SRV systemd[1]: Failed to start Docker Application Container Engine.
    Jan 03 12:40:03 SRV systemd[1]: Unit docker.service entered failed state.

    I just want to update my suggestion list based on what I saw in Docker for OMV3 (I had OMV2 at the time).

    I'll try to scavenge the source code and collaborate... don't know if I know enough web development for this.

    Another thing: when MODIFY or COPY, the next screen (with container details) doesn't bring old stuff typed in "Extra args" field.


    I use "--link XXXXXX" a lot... so the Extra args are a need for me, while the GUI doesn't support the --link

    I had some trouble trying to modify containers... the error "Error: "Failed to connect to localhost port 80: Connection refused" - Code: 7" appears when I try to SAVE the changes.


    Can someone explain me what is happening?