snapcraft updates don't download in an IPv6 + NAT64 environment
Metadata
Current evaluation
IPv6-only/NAT64 hosts fail `snap install`: snapd dials api.snapcraft.io over IPv4 (91.189.92.20) with no v6 fallback. Fault is in the snap/snapd client, not snapcraft. Unlabelled, no maintainer response since 2019.
Suggested action: needs triage
Reason: The report reproduces cleanly (`dial tcp 91.189.92.20:443: connect: network is unreachable` on IPv6+NAT64, workaround via /etc/hosts per the reporter's 2019-12-20 comment), but the failing code is the `snap` client, not this repo: grepping snapcraft for `api.snapcraft.io`, `snaps/refresh`, `persistent network error`, `AF_INET6`, and `NAT64` yields only test fixtures in tests/unit/store/test_client.py and proxy plumbing in snapcraft/providers.py — no IPv6 dial logic exists here, so no fix commit could exist in this history. The bug also has never been assessed: zero labels and the only comment is from the reporter, so a maintainer needs to reassign/transfer it to snapd (Launchpad invalid/misfiled). Impact is real but bounded to IPv6-only hosts and belongs to another codebase, while actionability here is low because the proposed fix has no landing site in snapcraft.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
2
Complexity:
75
Confidence:
72
Actionability:
25
|
needs triage | IPv6-only/NAT64 hosts fail `snap install`: snapd dials api.snapcraft.io over IPv4 (91.189.92.20) with no v6 fallback. Fault is in the snap/snapd client, not snapcraft. Unlabelled, no maintainer response since 2019. | |
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
8
Complexity:
62
Confidence:
76
Actionability:
62
|
needs triage | Snap install/refresh fails on IPv6-only+NAT64 hosts: `snap install` dials api.snapcraft.io's unreachable IPv4 (91.189.92.20) with no IPv6 fallback. Reporter suggests preferring v6 or falling back. No maintainer triage since 2019. | |
| stealth/space-bunny-alpha |
Impact:
63
Quick Win:
20
Complexity:
58
Confidence:
86
Actionability:
75
|
needs triage | Snap installs and refreshes fail on IPv6-only NAT64 networks because snapd attempts api.snapcraft.io over an unreachable IPv4 address instead of synthesized IPv6. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
16
Staleness:
95
Complexity:
60
Confidence:
55
Support Request:
10
|
needs triage | Snap installer/refresh hardcodes IPv4 (dial tcp 91.189.92.20:443) and fails on IPv6-only + NAT64 networks where api.snapcraft.io is reachable only via synthesized IPv6. No maintainer response, no labels, no comments; open ~6.7 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
10
|
close stale | Issue reports snapcraft installer failing in IPv6+NAT64 environments by ignoring IPv6 and attempting direct IPv4 connections. Unaddressed for over 6 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
15
|
close stale | Snapcraft fails to connect via IPv6/NAT64, hardcoding IPv4 and causing network errors. Unlabeled, zero comments, inactive for over six years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
65
Confidence:
85
Support Request:
10
|
close stale | Snapcraft fails to install or update in IPv6-only/NAT64 environments due to IPv4 preference and lack of IPv6 fallback. Unlabelled, no maintainer response, inactive for ~6.5 years. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1782246 Unable to use snaps in an IPV6 only setup | snapcraft (launchpad) | open | Asks for snaps to work on IPv6-only hosts: 'snap login' fails dialing dashboard.snapcraft.io's IPv4 address. Untriaged, zero comments; failure is in the snap client/store infra, not the snapcraft tool. |