Simon Fels a8704556da Unload AppArmor profile for container management process ... If we run the management process with the AppArmor profile loaded from snap-confine various ashmem/binder operations are failing with permission denied errors. To workaround this until this problem is fixed we simply unload the AppArmor profile and continue to execute completely without any profile loaded.		2016-12-04 17:07:44 +01:00
..
anbox-bridge.sh	Add copyright header for bridge script	2016-11-27 16:02:53 +01:00
anbox-init.sh	Rework container management	2016-08-14 15:50:16 +02:00
android-sync.sh	Add simple sync script for Android builds	2016-11-11 09:57:44 +01:00
clean-format.sh	Reformat all code and use the Google cpp code style	2016-12-02 17:38:43 +01:00
container-manager.sh	Unload AppArmor profile for container management process	2016-12-04 17:07:44 +01:00
container-shell.sh	Specify android root path for container	2016-10-21 19:55:22 +02:00
create-package.sh	Simplify rootfs creation script by using existing env variable	2016-08-14 15:53:01 +02:00
iptables-wrapper	Initial work	2016-06-14 11:34:17 +02:00
launch-abox.sh	Initial work	2016-06-14 11:34:17 +02:00
load-kmods.sh	Add simple script to build and load relevant kernel modules	2016-11-28 07:34:26 +01:00
setup-partial-armhf-chroot.sh	Initial work	2016-06-14 11:34:17 +02:00
setup-rootfs.sh	Fix name of the android rootfs tarball	2016-09-17 10:48:24 +02:00
shell.sh	Extend snap packaging with further details	2016-09-17 10:48:07 +02:00
snap-wrapper.sh	Extend snap packaging with further details	2016-09-17 10:48:07 +02:00
start-container.sh	Extend snap packaging with further details	2016-09-17 10:48:07 +02:00