Unable to start the container

[Antony Callistus]

i was able to create the container bu t i was not able to start the it , it shows

Job for pve-container@104.service failed because the control process exited with error code.
See "systemctl status pve-container@104.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@104' failed: exit code 1

in systemctl status pve-container@104.service

● pve-container@103.service - PVE LXC Container: 103
Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2019-02-01 15:27:20 IST; 6min ago
Docs: man:lxc-start
man:lxc
manct
Process: 1957597 ExecStart=/usr/bin/lxc-start -n 103 (code=exited, status=1/FAILURE)

Feb 01 15:27:20 pve systemd[1]: Starting PVE LXC Container: 103...
Feb 01 15:27:20 pve lxc-start[1957597]: lxc-start: 103: confile.c: parse_line: 1994 Unknown configuration key "lxc.apparmor.raw"
Feb 01 15:27:20 pve lxc-start[1957597]: lxc-start: 103: parse.c: lxc_file_for_each_line: 58 Failed to parse config: lxc.apparmor.raw
Feb 01 15:27:20 pve lxc-start[1957597]: lxc-start: 103: tools/lxc_start.c: main: 289 Failed to create lxc_container
Feb 01 15:27:20 pve systemd[1]: pve-container@103.service: Control process exited, code=exited status=1

 

[bvanhoof]

We have the same issue. We did the following as a workaround :

1) Comment all lines containing 'lxc.apparmor' in the lxc config file:​

sed -i 's/^lxc.apparmor/#lxc.apparmor/' /var/lib/lxc/<CTID>/config​

2) Start the container by CLI instead of using the GUI :

lxc-start --name=<CTID>​

(We are still using proxmox 5.1)