Posts by sfu420

    At the weekend i've decided to upgrade my NAS to OMV v5 with a clean install and run into exactly the same problem and error message.
    Portainer won't start with Proxmox kernel only with Debian's one. After 3 days of tinkering finally i have figured out what the heck is going on:
    If you use Debian Netinst ISO, it will automatically install AppArmor by default, instead OMV does not.
    And the reason of this error message is, that AppArmor finds Portainer as a security threat and blocks it. Check dmesg and you will see it.
    So you have 3 options to solve it:

    • Add  --security-opt apparmor:unconfined  option to the docker run command
    • Create new/modify the docker-default security profile in /etc/apparmor.d as described in Docker Doc:
    • Remove AppArmor completely from the system:  apt-get --yes purge --autoremove apparmor 

    I choosed the third one, for now :)

    But the big question still remains. Why behaves AppArmor with these kernels differently, even if docker-default profile remains still the same.

    Or just convert your docker environment into a single node swarm cluster with the following CLI command.
    After this, Portainer will be able to handle docker-compose v3 in the GUI ;)

    docker swarm init

    If you would like to add more extra feature to Portainer, you can use Portainer Agent as well.
    IMPORTANT: Please adjust directory path in line 8 accordingly to your environment (where are your docker volumes located).
    After that you will be able to browse content of docker volumes in Portainer or even upload files into them.

    Requirement: Your old Portainer container have to have a volume with name "portainer_data" in order to keep settings!

    Same error. :(

    The backports kernel installation works like a charm on a VM installed with openmediavault-3.0.36.iso.

    But OMV installed on pure Debian works not. What is the difference??? I can't figure it out.

    Yes, that was the difference between the 2 installs.

    Installed with your ISO openmediavault_3.0.36-amd64.iso
    the /etc/apt/sources.list file is:

    deb jessie main
    deb-src jessie main

    deb jessie/updates main contrib non-free
    deb-src jessie/updates main contrib non-free

    # jessie-updates, previously known as 'volatile'
    deb jessie-updates main contrib non-free
    deb-src jessie-updates main contrib non-free

    and installed with the debian-8.6.0-amd64-netinst.iso
    the /etc/apt/sources.list file was:

    deb jessie main
    deb-src jessie main

    deb jessie/updates main
    deb-src jessie/updates main

    # jessie-updates, previously known as 'volatile'
    deb jessie-updates main
    deb-src jessie-updates main

    So I completed the necessary lines with "contrib non-free", and clicked on the APT Clean button, but i got the same issue.

    Have you any other idea?

    There is only firmware-linux-free instead of firmware-linux package in the repo.

    root@openmediavault:~# apt-cache search firmware-linux
    firmware-linux-free - Binary firmware for various drivers in the Linux kernel

    No. I had internet.
    I installed it with this method, because i need crypted rootfs:

    I used the Debian 8.6-netinst.iso
    All options are unchecked, when the installer asked for packages.

    After reboot:
    echo "deb erasmus main" > /etc/apt/sources.list.d/openmediavault.list

    apt-get update
    apt-get install openmediavault-keyring postfix
    When the ‘Postfix Configuration’ dialogue is displayed choose “No configuration”.

    apt-get update
    apt-get install openmediavault
    shutdown -r now

    And after that i installed the lvm plugin without any problem.

    OMV v3.0.50 and OMV-Extras v3.4.4


    if i'm trying to install the backports kernel i got this error message in OMV-Extras:

    How to fix this?

    This system is a fresh install.