systemd v239 (networkd && resolved) containers broken by AA

Discussion in 'Proxmox VE: Networking and Firewall' started by jwh, Jul 13, 2018.

  1. jwh

    jwh New Member

    Joined:
    Jul 13, 2018
    Messages:
    3
    Likes Received:
    1
    Hi guys,

    Just stumbled across this one - using Arch in a container, once upgraded to v239 (which uses dynamic users for networkd and resolved), AA seems to be breaking it for some reason, setting the profile to unconfined allows it to work - unprivileged container is not enough

    Just wondering if anyone had come across this yet?

    Container journal:

    systemd[51]: systemd-networkd.service: Failed to update dynamic user credentials: Permission denied
    systemd[51]: systemd-networkd.service: Failed at step USER spawning /usr/lib/systemd/systemd-networkd: Permission denied
     
    #1 jwh, Jul 13, 2018
    Last edited: Jul 13, 2018
    BerndA likes this.
  2. jwh

    jwh New Member

    Joined:
    Jul 13, 2018
    Messages:
    3
    Likes Received:
    1
    So it's actually being denied the ability to create a lock on a socket it would appear?

    Jul 14 16:47:44 vm1 audit[3315869]: AVC apparmor="DENIED" operation="file_lock" profile="lxc-container-default-cgns" pid=3315869 comm="systemd" family="unix" sock_type="dgram" protocol=0 addr=none
    Jul 14 16:47:44 vm1 audit[3315869]: AVC apparmor="DENIED" operation="file_lock" profile="lxc-container-default-cgns" pid=3315869 comm="systemd" family="unix" sock_type="dgram" protocol=0 addr=none
    Jul 14 16:47:44 vm1 audit[3316074]: AVC apparmor="DENIED" operation="file_lock" profile="lxc-container-default-cgns" pid=3316074 comm="(networkd)" family="unix" sock_type="dgram" protocol=0 addr=none
    Jul 14 16:47:44 vm1 audit[3316074]: AVC apparmor="DENIED" operation="file_lock" profile="lxc-container-default-cgns" pid=3316074 comm="(networkd)" family="unix" sock_type="dgram" protocol=0 addr=none
    Jul 14 16:47:44 vm1 audit[3316074]: AVC apparmor="DENIED" operation="file_lock" profile="lxc-container-default-cgns" pid=3316074 comm="(networkd)" family="unix" sock_type="dgram" protocol=0 addr=none
    Jul 14 16:47:44 vm1 audit[3316074]: AVC apparmor="DENIED" operation="file_lock" profile="lxc-container-default-cgns" pid=3316074 comm="(networkd)" family="unix" sock_type="dgram" protocol=0 addr=none

    How do I tell this apparmor nonsense to allow it?
     
  3. wbumiller

    wbumiller Proxmox Staff Member
    Staff Member

    Joined:
    Jun 23, 2015
    Messages:
    573
    Likes Received:
    64
  4. jwh

    jwh New Member

    Joined:
    Jul 13, 2018
    Messages:
    3
    Likes Received:
    1
    Ah I didn't come across those, makes sense!

    Are you guys going to wait until its backported?
     
  5. wbumiller

    wbumiller Proxmox Staff Member
    Staff Member

    Joined:
    Jun 23, 2015
    Messages:
    573
    Likes Received:
    64
    Depends on how long it takes. The fixes need to appear upstream first.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice