Multiple cgroups/cgfsng.c and other related errors when attempting to start containers using lxc-start

Hello, I wanted to ask for help regarding the problem I am experiencing with LXC.
I am attempting to create a Debian Stretch container on a Debian Stretch 9.4 host running on an ODORID-C2 (ARMv8-A 64bit, arm64) with a 3.16 kernel. My LXC version is 2.0.7

Like my other devices I own, running the lxc-create command as root user
“sudo MIRROR= lxc-create -n test-cont -t /usr/share/lxc/templates/lxc-debian – -r stretch -a arm64”
successfully activates debootstrap, downloads pakages, and sets up the container.

However, when I attempt to start up the container with “'lxc-start -n test-cont -d”, it does not work.

lxc-start: tools/lxc_start.c: main: 366 The container failed to start.
lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode.
lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options.

I issued a ‘lxc-start -n test-cont --logfile test-cont-trace.txt --logpriority trace’ command to get the full trace

And I also appended the ‘lxc.aa_allow_incomplete = 1’ to my container configuration file and did another trace

Both of those logs were rather long so I’ve uploaded both of them to Google Drive in .txt format.

How can I get my containers to start up? Also, the logs show references to AppArmor but ‘apt policy apparmor’ shows that I don’t have it installed…

After a few hours of digging around I found a way around the AppArmor problem!
I put the ‘lxc.aa_profile = unconfined’ in my container configuration file and my container NOW STARTS!