Unable to use snaps in an IPV6 only setup
Metadata
Current evaluation
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.
Suggested action: needs triage
Reason: The report has no labels, no assignee and no maintainer comments, so it has never been assessed; the author even states "I'm not sure if this is really the right place for this as it is not really a bug" and asks where to reach out. The failing command is `sudo snap login` (error text: "cannot get snap access permission from store: Post https://dashboard.snapcraft.io/dev/api/acl/"), i.e. the snap client's HTTP transport resolving 91.189.92.17 (IPv4), not anything in this repository — greps for ipv6/AF_INET/socket in snapcraft and `git log --grep=ipv6` return nothing, and the store client here only holds the URL constant `STORE_URL = "https://dashboard.snapcraft.io"`. A maintainer should redirect it to the snapd/store-service owner; confidence is limited because I found no maintainer commentary and no related snapcraft issue to confirm ownership of the snapcraft.io endpoint.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
25
Quick Win:
2
Complexity:
80
Confidence:
68
Actionability:
35
|
needs triage | 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. | |
| stealth/space-bunny-alpha |
Impact:
58
Quick Win:
6
Complexity:
80
Confidence:
76
Actionability:
48
|
needs triage | IPv6-only hosts cannot access the Snap Store because the login endpoint resolves to an unreachable IPv4 address. This old report lacks current retesting or maintainer triage. | |
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
18
Staleness:
95
Complexity:
40
Confidence:
45
Support Request:
55
|
close stale | Request for IPv6 support so snaps work in IPv6-only environments; snap login fails dialing an IPv4 store endpoint (91.189.92.17). 8 years old, no labels, zero comments, no maintainer interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
30
Confidence:
85
Support Request:
90
|
close stale | Feature request for IPv6 support on snapcraft.io. Open for 8 years with zero maintainer comments or labels. Reporter notes connection failures due to IPv4-only store endpoints and asks for IPv6-only environment compatibility. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
60
Confidence:
90
Support Request:
85
|
needs triage | User reports inability to use snaps on IPv6-only networks due to snapcraft.io resolving to IPv4. No maintainer response or labels after ~8 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
40
Confidence:
85
Support Request:
80
|
close stale | Request to add IPv6 support for snapcraft.io and the Snap store, as IPv4-only endpoints prevent usage in IPv6-only environments. Untriaged and inactive for ~8 years. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1857006 snapcraft updates don't download in an IPv6 + NAT64 environment | snapcraft (launchpad) | open | 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. |