Refreshing snapd while running snapcraft fails with empty response from server
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Closed without comments or resolution after ~78 days. Likely abandoned or marked stale. No fix or workaround was implemented.
Suggested action: —
No scores available.
Issue body
Running `snapcraft --use-lxd` results in the following error:
```
Launching a container.
Waiting for container to be ready
Waiting for network to be ready...
error: cannot refresh "snapd": unexpectedly empty response from the server (try again later)
```
This error is happening from inside the lxd container. The container has internet connectivity as shown from these commands executed manually from within the container:
```
snapcraft-alusus # snap list
Name Version Rev Tracking Publisher Notes
core18 20211028 2253 latest/stable canonical✓ base
core20 20211115 1242 latest/stable canonical✓ base
snapcraft 5.0 6751 latest/stable canonical✓ classic
snapd 2.52.1 13640 latest/stable canonical✓ snapd
snapcraft-alusus # snap refresh snapd
error: cannot refresh "snapd": unexpectedly empty response from the server (try again later)
snapcraft-alusus # snap refresh
All snaps up to date.
snapcraft-alusus # snap refresh core18
snap "core18" has no updates available
snapcraft-alusus # snap refresh core20
snap "core20" has no updates available
snapcraft-alusus # snap refresh snapcraft
snap "snapcraft" has no updates available
snapcraft-alusus # snap refresh snapd
error: cannot refresh "snapd": unexpectedly empty response from the server (try again later)
snapcraft-alusus # apt update
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Get:2 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Get:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:4 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [876 kB]
Fetched 1103 kB in 2s (579 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
snapcraft-alusus #
```
As you see, only the snapd package is having the issue; other packages can be refreshed successfully. Also, the `apt update` command is running successfully, so there is no connectivity issue.
This issue has been going for hours. I thought the servers could be down, but the issue is only happening with snapd package, and the snapcraft status page is all green.
Is there a way to tell snapcraft to skip refreshing so at least I can unblock myself for now?
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without comments or resolution after ~78 days. Likely abandoned or marked stale. No fix or workaround was implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution or comments. The report details a snapd refresh failure inside LXD containers during snapcraft builds, but no fix, workaround, or maintainer response was provided, indicating the report was abandoned or marked stale. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution due to inactivity. The report described an empty server response when refreshing snapd inside an LXD container during snapcraft execution. No fix was provided, and the thread was abandoned. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1615764 Support snapcraft close | snapcraft (launchpad) | closed | The requested snapcraft close command was closed without implementation. It appears abandoned due to prolonged inactivity, with zero comments or development activity after opening. | |
| #1746784 Failing while fetching parts.snapcraft.io should be handled better | snapcraft (launchpad) | closed | Closed without comments or resolution. No fix or merge details provided; likely abandoned or marked stale. | |
| #1789206 cannot rebuild snapcraft | snapcraft (launchpad) | closed | Closed without resolution. The request to enable snapcraft self-rebuilding via build caching was abandoned due to prolonged inactivity and lack of implementation. | |
| #1666908 Create a snapcraft snap | snapcraft (launchpad) | closed | Closed without implementation. The request to package snapcraft as a snap was abandoned after nearly a decade with no comments or follow-up action. | |
| #1663625 No script named 'snapcraft' | snapcraft (launchpad) | closed | A report of snapcraft failing after apt installation was closed without resolution or comments, indicating the matter was abandoned. | |
| #1448 snapcraft build using manifest.yaml | snapcraft | closed | Closed without discussion or comments. The issue appears abandoned or superseded by newer snapcraft build workflows. No resolution or merge details were recorded. | |
| #1723965 snapcraft doesn't work | snapcraft (launchpad) | closed | Closed without resolution or comments, indicating abandonment. The reported snap command failure and GL driver errors remain unresolved. | |
| #1633613 useless "no such file or directory" message | snapcraft (launchpad) | closed | A confusing snapcraft error message report was closed without comments or resolution, likely abandoned due to prolonged inactivity. No fix or workaround was implemented. | |
| #1956216 Snapcraft is no longer working within a Docker container | snapcraft (launchpad) | closed | Closed without resolution. The report detailed a snapcraft ModuleNotFoundError in Docker containers, but received no comments or fixes. The issue remains abandoned. | |
| #2013112 Installing snapcraft under a different name causes version mixup | snapcraft (launchpad) | closed | The snapcraft parallel install version mixup was closed without resolution. With zero comments and over three years of inactivity, the bug was abandoned and remains unfixed. |