zerobyte: disable apparmor when mount fuse is enabled

ix-dev/community/zerobyte/app.yaml

@@ -32,4 +32,4 @@ sources:
 - https://github.com/nicotsx/zerobyte
 title: Zerobyte
 train: community
-version: 1.1.16
+version: 1.1.17

ix-dev/community/zerobyte/questions.yaml

@@ -51,7 +51,7 @@ questions:
         - variable: mount_fuse
           label: Mount FUSE / Add SYS_ADMIN Capability
           description: |
-            Mount the FUSE device inside the container and add the SYS_ADMIN capability.</br>
+            Mount the FUSE device inside the container, adds the SYS_ADMIN capability and sets apparmor to unconfined.</br>
             This is required for mounting remote backends like SMB, NFS, rclone, etc.</br>
             WARNING: This will give the container very high privileges on the host system,</br>
             including the potential to interact with or damage ZFS pools and datasets.</br>
@@ -239,7 +239,8 @@ questions:
                                           "null": true
                                       - variable: priority
                                         label: Priority (Optional)
-                                        description: Indicates in which order Compose connects the service's containers to its networks.
+                                        description: Indicates in which order Compose connects the service's containers
+                                          to its networks.
                                         schema:
                                           type: int
                                           "null": true

ix-dev/community/zerobyte/templates/docker-compose.yaml

@@ -12,6 +12,7 @@
   {% endif %}
   {% do c1.add_caps(["SYS_ADMIN"]) %}
   {% do c1.devices.add_device("/dev/fuse", "/dev/fuse") %}
+  {% do c1.add_security_opt("apparmor", "unconfined") %}
 {% endif %}
 
 {% do c1.healthcheck.set_test("wget", {"port": values.consts.internal_web_port, "path": "/api/healthcheck"}) %}