more transparency for container build in first charmcraft pack
Metadata
Current evaluation
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.
Suggested action: —
No scores available.
Issue body
When I ran the `charmcraft pack` command for the first time on a machine that had firewalls enabled, I wasn't sure how long the creation of the build container should take. I let it run for 90 minutes without it completing and then cancelled the command. The issue ended up being that I had enabled a firewall that was preventing charmcraft from being able to communicate with the lxd container which is why the command was stuck. It could have potentially helped to:
- Check the machine to any potential issues (such as firewall rules blocking traffic to the lxd container)
- Include more information about how long the command should take to execute and
- Include more information about what is going on to help the user determine whether a given action is taking a reasonable amount of time or whether there is likely to be an issue with the development environment.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | 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. | |
| qwen/qwen3.6-35b-a3b | — | — | Superseded by upstream fix. The charmcraft pack command hangs on DNS lookups when firewalls block LXD traffic. Maintainers opened an issue in the craft-providers library to add a timeout. The fix will be implemented upstream. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed as resolved upstream. The pack command hung on DNS resolution due to a missing timeout in craft-providers. A fix was opened in the craft-providers library to add timeouts and progress feedback, applied transparently to charmcraft. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed. The hang stemmed from a missing network timeout in craft-providers when firewalls block LXD traffic. Upstream issue #146 tracks the fix, which will resolve this transparently. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #660 `charmcraft pack` fails with error writing to lxd unix socket | charmcraft | closed | 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. | |
| #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. | |
| #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. |