Skip to content

Commit 2f13232

Browse files
committed
Only update AppArmor profile if not chroot'ed
This prevents `postinst` script failure when run in a `chroot` environment. This closes #8841.
1 parent 6ac8f91 commit 2f13232

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

packages/app-builder-lib/templates/linux/after-install.tpl

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,10 @@ if test -d "/etc/apparmor.d"; then
4242
if apparmor_parser --skip-kernel-load --debug "$APPARMOR_PROFILE_SOURCE" > /dev/null 2>&1; then
4343
cp -f "$APPARMOR_PROFILE_SOURCE" "$APPARMOR_PROFILE_TARGET"
4444

45-
if hash apparmor_parser 2>/dev/null; then
45+
# Updating the current AppArmor profile is not possible and probably not meaningful in a chroot'ed environment.
46+
# Use cases are for example environments where images for clients are maintained.
47+
# There, AppArmor might correctly be installed, but live updating makes no sense.
48+
if ! { [ -x '/usr/bin/ischroot' ] && /usr/bin/ischroot; } && hash apparmor_parser 2>/dev/null; then
4649
# Extra flags taken from dh_apparmor:
4750
# > By using '-W -T' we ensure that any abstraction updates are also pulled in.
4851
# https://wiki.debian.org/AppArmor/Contribute/FirstTimeProfileImport

0 commit comments

Comments
 (0)