Beiträge von namron

Sorry, I can't tell.

I just installed docker manually following the instructions from docker.com.

sudo apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin

and now I got version 20.10.17 and the apparmor-issue is gone.

Thanks for all the help!

I don't understand where this docker version comes from. My sources all look good to me:

sources.list                            
16:deb [arch=amd64] https://download.docker.com/linux/debian bullseye stable 
17:# deb-src [arch=amd64] https://download.docker.com/linux/debian bullseye stable 

Re-installing (with omv-installdocker) gets me the same version again:

Setting up docker.io (20.10.5+dfsg1-1+deb11u1) ...  

My docker version is Server Version: 20.10.5+dfsg1 

Sure, it's only a workaround, that's why I called it so.

I get the exact same results as you:

❯ cat /sys/module/apparmor/parameters/enabled
Y
❯ dpkg -l | grep appa
ii  libapparmor1:amd64                  2.13.6-10                      amd64        changehat AppArmor library

docker info still thinks apparmor is on:

❯ docker info
Client:
 Context:    default
 Debug Mode: false
...
 Security Options:
  apparmor
  seccomp
   Profile: default
  cgroupns
...

EDIT:

I found out, that explicitly disabling AppArmor per service is a workaround:

security_opt:         
  - apparmor:unconfined 

I ran

apt-get purge apparmor apparmor-utils auditd

just to make sure they are completely gone and rebooted afterwards.

no /etc/apparmor.d:

❯ sudo ls -al /etc/apparmor.d/
ls: cannot access '/etc/apparmor.d/': No such file or directory

I purged the apparmor packages, that's the output now:

dpkg -l | grep apparmor                                                                      
ii  libapparmor1:amd64                  2.13.6-10                      amd64        changehat AppArmor library

Still the same error when trying to start a docker container.

A reboot did not help. It somehow still detects AppArmor as installed.

Could it be that the proxmox kernel has it enabled, and that's what docker checks?

Hi,

I just finished upgrading from v5 to v6.0.29. The upgrade itself went very smooth, thanks for that!

Afterwards I upgraded my kernel to 5.15.35-2-pve (Proxmox because I use ZFS).

When I then tried to start my docker containers it failed claiming AppArmor is enabled, but the docker-default profile is missing:

ERROR: for XXX  Cannot start service jackett: AppArmor enabled on system but the docker-default profile could not be loaded: running `apparmor_parser apparmor_parser --version` failed with output: 
error: exec: "apparmor_parser": executable file not found in $PATH

Linux 5.15.35-2-p

But the apparmor-package is not installed, as seems to be the default for OMV:

dpkg --list | grep apparmor
rc  apparmor                            2.13.6-10                      amd64        user-space parser utility for AppArmor
rc  apparmor-utils                      2.13.6-10                      amd64        utilities for controlling AppArmor
ii  libapparmor1:amd64                  2.13.6-10                      amd64        changehat AppArmor library

B

I completely removed docker and reinstalled it using omv-installdocker, but this has not helped. Any idea what might have gone wrong here?

I found the solution in another thread here on the forum:

Zitat von siddhartha

I had this problem as well. This fixed it for me:

• Check to see if you have a file /sbin/start-stop-daemon.REAL
• If you do:
  
  
  • mv /sbin/start-stop-daemon.REAL /sbin/start-stop-daemon

Supposedly this should be done after the OS installation, but for some reason it is not triggered.

Hello,

just wanted to give the new OMV version a spin, but I encounter some problems with NFS.

I setup everything like I had on my OMV2 installation, yet:

showmount -e OMV3IP
RPC: Port mapper failure - Unable to receive: errno 111 (Connection refused)


rpcinfo -p OMV3IP 
RPC: Port mapper failure - Unable to receive: errno 111 (Connection refused)

But on the OMV3 box everything seems fine:

service rpcbind status
● rpcbind.service - LSB: RPC portmapper replacement
   Loaded: loaded (/etc/init.d/rpcbind)
  Drop-In: /run/systemd/generator/rpcbind.service.d
           └─50-rpcbind-$portmap.conf
   Active: active (exited) since Fri 2017-05-19 15:34:15 CEST; 9min ago
  Process: 1127 ExecStart=/etc/init.d/rpcbind start (code=exited, status=0/SUCCESS)


May 19 15:34:15 omv3 rpcbind[1127]: Starting rpcbind daemon...
May 19 15:34:15 omv3 rpcbind[1127]: Warning: Fake start-stop-daemon called, doing nothing.
May 19 15:34:15 omv3 rpcbind[1127]: .
May 19 15:34:15 omv3 systemd[1]: Started LSB: RPC portmapper replacement.
May 19 15:43:43 omv3 systemd[1]: Started LSB: RPC portmapper replacement.

and:

root@omv3:~# cat /etc/exports
# This configuration file is auto-generated.
# WARNING: Do not edit this file, your changes will be lost.
#
# /etc/exports: the access control list for filesystems which may be exported
#               to NFS clients.  See exports(5).
/export/test1 192.168.11.0/24(fsid=1,rw,subtree_check,secure)
# NFSv4 - pseudo filesystem root
/export 192.168.11.0/24(ro,fsid=0,root_squash,no_subtree_check,hide)

Both machines, client and OMV3, are in the same subnet.
I can ping from one to the respective other.

What could be the issue here?

I still have the same issue with virtio drives. SMART properties are shown in GUI, but when I try to run tests from the GUI I still get the message

/dev/vda: Unable to detect device type
Smartctl: please specify device type with the -d option.

Cant you include a field in the GUI to specify the device type?

Regards,

Norman