Ho installato un sacco di container LXC. Uno di questi contiene una directory che sto condividendo tramite SMB.
Quegli LXC che montano questo contenitore SMB usando CIFS non si avviano più, né l'host. Tutti gli LXC che non fanno riferimento a questa condivisione iniziano bene.
Sto usando proxmox con la seguente stringa di versione: Linux pve 4.15.18-9-pve #1 SMP PVE 4.15.18-30ho impostato il repository non abbonato e tutto è completamente aggiornato.
Prima del riavvio del server, gli LXC si accendevano / spegnevano perfettamente e montavano la condivisione CIFS con il file fstab.
journalctl -xe fornisce il seguente output:
ec 17 16:18:15 pve systemd[1]: Starting PVE LXC Container: 104...
-- Subject: Unit pve-container@104.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pve-container@104.service has begun starting up.
Dec 17 16:18:16 pve audit[2081]: AVC apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="/usr/bin/lxc-start" name="lxc-104_</var/lib/lxc>" pid=2081 comm="apparmor_parser"
Dec 17 16:18:16 pve kernel: audit: type=1400 audit(1545063496.397:48): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="/usr/bin/lxc-start" name="lxc-104_</var/lib/lxc>" pid=2081 comm="apparmor_parser"
Dec 17 16:18:16 pve kernel: IPv6: ADDRCONF(NETDEV_UP): veth104i0: link is not ready
Dec 17 16:18:16 pve systemd-udevd[2082]: Could not generate persistent MAC address for veth40AWVM: No such file or directory
Dec 17 16:18:16 pve kernel: vmbr0: port 4(veth104i0) entered blocking state
Dec 17 16:18:16 pve kernel: vmbr0: port 4(veth104i0) entered disabled state
Dec 17 16:18:16 pve kernel: device veth104i0 entered promiscuous mode
Dec 17 16:18:16 pve kernel: eth0: renamed from veth40AWVM
Dec 17 16:18:17 pve kernel: vmbr0: port 4(veth104i0) entered disabled state
Dec 17 16:18:17 pve kernel: device veth104i0 left promiscuous mode
Dec 17 16:18:17 pve kernel: vmbr0: port 4(veth104i0) entered disabled state
Dec 17 16:18:17 pve systemd[1]: pve-container@104.service: Control process exited, code=exited status=1
Dec 17 16:18:17 pve systemd[1]: pve-container@104.service: Killing process 2073 (lxc-start) with signal SIGKILL.
Dec 17 16:18:17 pve systemd[1]: pve-container@104.service: Killing process 2183 (apparmor_parser) with signal SIGKILL.
Dec 17 16:18:17 pve systemd[1]: Failed to start PVE LXC Container: 104.
-- Subject: Unit pve-container@104.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit pve-container@104.service has failed.
--
-- The result is failed.
Dec 17 16:18:17 pve systemd[1]: pve-container@104.service: Unit entered failed state.
Dec 17 16:18:17 pve systemd[1]: pve-container@104.service: Failed with result 'exit-code'.
Dec 17 16:18:17 pve pvedaemon[2064]: command 'systemctl start pve-container@104' failed: exit code 1
Dec 17 16:18:17 pve pvedaemon[31031]: <root@pam> end task UPID:pve:00000810:000DC32A:5C17CC47:vzstart:104:root@pam: command 'systemctl start pve-container@104' failed: exit code 1
Varie risposte sui forum di proxmox suggeriscono il downgrade di apparmor a una versione da jessie-backport. Ho provato questo e non ha aiutato.
Qualche idea?