`charmcraft pack` fails with error writing to lxd unix socket
Metadata
Current evaluation
A transient LXD socket timeout stopped packing; `charmcraft clean` restored operation, the error did not recur, and the reporter closed the report without a code fix.
Resolution: closed not a bug
Reason: The reporter confirmed that cleaning restored packing and that the socket timeout had not recurred before closing on February 24, 2022. No resolving PR or commit was identified, indicating an isolated local or LXD-state failure.
Evaluated by: mr-cal-bot
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | A transient LXD socket timeout stopped packing; `charmcraft clean` restored operation, the error did not recur, and the reporter closed the report without a code fix. | |
| stealth/space-bunny-alpha | — | closed stale | Transient LXD unix socket i/o timeout during `charmcraft pack`; reporter confirmed it never recurred after `charmcraft clean` and self-closed with no code fix. | |
| stealth/space-bunny-alpha | — | closed not a bug | Reporter hit a local LXD unix.socket i/o timeout during `charmcraft pack`; `charmcraft clean` worked around it and the error never recurred, so sed-i self-closed #660 with no code change. | |
| stealth/space-bunny-alpha | — | closed not a bug | charmcraft pack worked after charmcraft clean; the reporter confirmed the LXD socket timeout had not recurred and closed #660, with no code fix. | |
| stealth/space-bunny-alpha | — | closed stale | Author closed the report after the LXD socket timeout did not recur; `charmcraft clean` worked around it. No code changes or resolving PR were reported. | |
| 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. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1594 Running `charmcraft pack` fails and returns `Instance setup failed. Check LXD logs for more details` | charmcraft | closed | Closed as an environment conflict, not a Charmcraft defect: Docker had changed networking in a way that interfered with LXD, and the reporter confirmed that uninstalling Docker and restarting fixed it. | |
| #815 charmcraft pack fails - connection timed out could not connect | charmcraft | closed | User-reported charmcraft pack failure was a local host/network problem (archive.ubuntu.com/security.ubuntu.com unreachable during apt cache update in the LXD build container). Author rebooted their machine and packing worked again, then self-closed the issue. | |
| #823 more transparency for container build in first charmcraft pack | charmcraft | closed | Firewall-blocked LXD setup hung `charmcraft pack` indefinitely on instance network setup. No charmcraft change needed; maintainer tracked the missing timeout in craft-providers and closed the issue. | |
| #497 charmcraft Pack is not Working | charmcraft | closed | Packaging succeeded after using the project owner with LXD permissions and cleaning stale state; the reporter confirmed the .charm file was created. | |
| #560 Charmcraft pack is giving error frequently | charmcraft | closed | The failure was traced to external LXD networking blocking access to archive.ubuntu.com during snapd installation; no Charmcraft fix was merged, and the reported firewall workaround did not help. | |
| #92 Suddenly getting charmcraft internal error with charmcraft pack | craft-providers | closed | Resolved upstream in LXD 4.23 revision 22525+, which corrected overly strict device-name validation; `snap revert lxd` was a temporary workaround. | |
| #511 `charmcraft pack` fails running `apt update` | charmcraft | closed | Closed with no Charmcraft code change: maintainers determined the `apt update` failure came from a broken host/LXD (fan bridge) networking setup, not a Charmcraft bug; guidance posted to Charmhub Discourse and the LXD forum. | |
| #2369 charmcract pack stuck at `Pausing control of the terminal` | charmcraft | open | First `charmcraft pack` hung ~30 min at 'Pausing control of the terminal' during LXD build; reporter saw it once and never answered maintainer's follow-up. | |
| #1338 `charmcraft clean` doesn't clean | charmcraft | closed | Closed unresolved: LXD cleanup remained broken in Charmcraft 3, with the changed behavior attributed to craft-application#425, which also closed without a linked fix. | |
| #646 Failed to inject host Charmcraft snap into target environment | charmcraft | closed | Report of charmcraft 1.4.0 failing to inject the host snap into the LXD build env. Closed without a code fix: a user fixed it with `charmcraft clean --verbose` and lengau closed it in Jan 2024 as not reproducible on current versions. |