`charmcraft pack` fails with error writing to lxd unix socket
Metadata
Current evaluation
charmcraft pack failed due to an LXD socket I/O timeout. The author closed the issue as the error did not recur after a clean rebuild. No code changes were applied.
Suggested action: —
No scores available.
Issue body
All of a sudden `charmcraft pack` fails with
```
invoke-rc.d: policy-rc.d denied execution of restart.
Error: write unix @->/var/snap/lxd/common/lxd/unix.socket: i/o timeout
```
After `charmcraft clean` I was able to `pack` successfully.
[charmcraft.log](https://github.com/canonical/charmcraft/files/8029237/charmcraft.log)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | charmcraft pack failed due to an LXD socket I/O timeout. The author closed the issue as the error did not recur after a clean rebuild. No code changes were applied. | |
| qwen/qwen3.6-35b-a3b | — | — | charmcraft pack failed with an LXD socket I/O timeout. Running charmcraft clean temporarily resolved it. The author confirmed the error did not recur and closed the issue as non-recurring. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | LXD socket timeout during charmcraft pack was worked around with charmcraft clean. The author confirmed the error did not recur and closed the issue as non-reproducible. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | The charmcraft pack LXD socket timeout error was reported but did not recur. The author closed the issue as non-reproducible after confirming the clean workaround resolved it. No code changes were applied. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #511 `charmcraft pack` fails running `apt update` | charmcraft | closed | Closed as out of scope. The failure stemmed from an LXD container networking bug, not charmcraft. No code changes were implemented; users were directed to external LXD and Discourse discussions for troubleshooting. | |
| #1594 Running `charmcraft pack` fails and returns `Instance setup failed. Check LXD logs for more details` | charmcraft | closed | Closed after the author confirmed uninstalling Docker resolved the conflict. Docker network settings interfered with LXD, causing charmcraft pack instance setup failures. Restarting the system after removal fixed the environment. | |
| #560 Charmcraft pack is giving error frequently | charmcraft | closed | Charmcraft pack failed due to an apt-get network error installing snapd in an LXD container. Maintainers linked it to a known networking issue. The reporter confirmed a workaround failed. Closed without a code fix, likely abandoned. | |
| #497 charmcraft Pack is not Working | charmcraft | closed | Resolved via user environment fix. The permission error stemmed from running charmcraft as root with root-owned files. Switching to a regular user, adding them to the lxd group, and correcting ownership allowed pack to succeed. No code changes required. | |
| #736 `charmcraft` lxc container starts failing with `FileNotFoundError` during iterative design | charmcraft | closed | Closed without a fix. Maintainer could not reproduce the LXC container corruption causing FileNotFoundError during charmcraft pack on newer versions. Reopen if reproducible on Charmcraft 2.7 or 3. | |
| #823 more transparency for container build in first charmcraft pack | charmcraft | closed | Closed as superseded. The charmcraft pack hang from firewall-blocked LXD traffic lacks a network timeout. A fix is tracked in craft-providers issue 146 and will be applied transparently to charmcraft. | |
| #647 `charmcraft build` sometimes fails on `apt install` inside the lxd container | charmcraft | closed | Closed as a duplicate of issue #567. The report details intermittent apt-get lock failures during charmcraft build inside LXD containers, suspected to be caused by unattended-upgrades. |