`charmcraft pack` fails on Resolute

Metadata

Project: charmcraft
Number: #2816
Type: issue
State: open
Author: jameinel
Labels: —
Created: 2026-08-07 04:41 PM UTC
Updated: 2026-08-07 04:41 PM UTC
Closed: —

Current evaluation

charmcraft pack fails on Ubuntu Resolute 26.04 host with Jammy container due to AppArmor protocol incompatibility. Untriaged, no maintainer response.

Suggested action: needs triage

Reason: The issue has no labels, no assignee, and zero maintainer comments despite being open 29 days. It presents a clear bug with reproduction steps and error logs showing AppArmor protocol incompatibility between Resolute 26.04 and Jammy 20.04 containers. A maintainer needs to assess whether this is a known limitation, a bug to fix, or if a workaround exists.

Impact: 50 Quick Win: 20.0 Staleness: 40 Complexity: 60 Confidence: 70 Support Request: 10

Issue body

### Check existing issues - [x] I've verified that this bug isn't described by any existing issues. ### Bug description It seems that there is an app-armor conflict between a Jammy container and a Resolute host when trying to `charmcraft pack`. When running I get this failure from charmcraft: ``` I'm trying to build the juju-controller charm, which wants a Jammy container. I just did ``` charmcraft pack ``` Using charmcraft 3. ### Steps to reproduce ``` git clone https://github.com/juju/juju-controller cd juju-controller sudo snap install charmcraft --classic --channel 3.x/stable charmcraft pack ``` Fails with: ``` charmcraft pack Failed to enable snapd service. * Command that failed: 'lxc --project charmcraft exec local:base-instance-charmcraft-buildd-base-v7--20d64a5acd5c317c9c8d -- env CRAFT_MANAGED_MODE=1 CHARMCRAFT_MANAGED_MODE=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical systemctl restart snapd.service' * Command exit code: 1 * Command standard error output: b'Job for snapd.service failed because the control process exited with error code.\nSee "systemctl status snapd.service" and "journalctl -xe" for details.\n' Full execution log: '/home/jameinel/.local/state/charmcraft/log/charmcraft-20260807-123357.396086.log' ``` Using lxc to investigate the container, I see this failure: ``` -- The unit tmp-syscheck\x2dmountpoint\x2d1453099174.mount has successfully entered the 'dead' state. Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: daemon.go:353: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s pe r snap) Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: backends.go:58: AppArmor status: apparmor is enabled and all features are available Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: cannot run daemon: state startup errors: [cannot reload snap-confine apparmor profile: cannot load apparmor profiles: exit status 185 Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: apparmor_parser output: Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: /sbin/apparmor_parser: Unable to replace "mount-namespace-capture-helper". Profile doe sn't conform to protocol Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: /sbin/apparmor_parser: Unable to replace "/usr/lib/snapd/snap-confine". Profile doesn' t conform to protocol Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: ] Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILUR E -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An ExecStart= process belonging to unit snapd.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 systemd[1]: snapd.service: Failed with result 'exit-code'. ``` From some searching "profile doesn't conform to protocol" seems that Jammy AppArmor is not compatible with Resolute. ### Environment Host is Ubuntu Resolute 26.04, container is Jammy 20.04. ### charmcraft.yaml ```yaml If the issue is specific to a project, share its `charmcraft.yaml`. This field automatically renders as YAML, so you don't need to add special formatting. ``` ### Log output ```shell -- Subject: A start job for unit snapd.service has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit snapd.service has begun execution. -- -- The job identifier is 1492. Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: overlord.go:274: Acquiring state lock file Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: overlord.go:279: Acquired state lock file Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: daemon.go:250: started snapd/2.67.1+20.04 (series 16; classic) ubuntu/20.04 (amd64) lin ux/7.0.0-29-generic. Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 systemd[1]: tmp-syscheck\x2dmountpoint\x2d1453099174.mount: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit tmp-syscheck\x2dmountpoint\x2d1453099174.mount has successfully entered the 'dead' state. Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: daemon.go:353: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s pe r snap) Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: backends.go:58: AppArmor status: apparmor is enabled and all features are available Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: cannot run daemon: state startup errors: [cannot reload snap-confine apparmor profile: cannot load apparmor profiles: exit status 185 Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: apparmor_parser output: Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: /sbin/apparmor_parser: Unable to replace "mount-namespace-capture-helper". Profile doe sn't conform to protocol Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: /sbin/apparmor_parser: Unable to replace "/usr/lib/snapd/snap-confine". Profile doesn' t conform to protocol Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 snapd[3063]: ] Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILUR E -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An ExecStart= process belonging to unit snapd.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 systemd[1]: snapd.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit snapd.service has entered the 'failed' state with result 'exit-code'. Aug 07 16:24:53 charmcraft-juju-controller-ubuntu-2004-amd64-4074305 systemd[1]: Failed to start Snap Daemon. ```

Evaluation history

Date	Model	Scores	Action	Summary
2026-09-06 01:58 AM UTC	qwen3.6-35b-a3b-mtp-q6	Impact: 50 Quick Win: 20.0 Staleness: 40 Complexity: 60 Confidence: 70 Support Request: 10	needs triage	charmcraft pack fails on Ubuntu Resolute 26.04 host with Jammy container due to AppArmor protocol incompatibility. Untriaged, no maintainer response.
2026-08-07 04:51 PM UTC	qwen/qwen3.6-35b-a3b	Staleness: 5 Complexity: 65 Confidence: 90 Support Request: 15	needs triage	charmcraft pack fails on Ubuntu Resolute 26.04 due to AppArmor protocol incompatibility when launching Jammy containers. Unlabelled, awaiting maintainer triage.

Update history

Date	Change
2026-08-07 04:41 PM UTC	created

Related work

Related To: canonical/charmcraft#1104 (confidence 75%)
Similar issue where charmcraft pack failed on a newer Ubuntu release (23.04) due to environment incompatibility, though the root cause was different (missing build environments vs AppArmor protocol mismatch).

Related issues

Issue	Project	State	Summary	Similarity
#1104 charmcraft pack on Ubuntu 23.04 (Lunar) fails.	charmcraft	closed	Charmcraft pack failed on Ubuntu 23.04 due to unavailable build environments. PR #1130 addressed the issue but was blocked by an external cloud-images bug. The issue was closed pending upstream resolution.	72%