← Back to issue list

Can’t run snapd on Codenvy 5.22.0

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1740851
Type
issue
State
open
Author
~20avva
Labels
—
Created
Updated
Closed
—

Current evaluation

snap install fails in a Codenvy (Eclipse Che) container workspace: /run/snapd.socket missing so snapd is unreachable, while snapcraft itself builds fine. No maintainer response; still open, later user reports the same error on s390x Launchpad builds.

Suggested action: needs triage

Reason: The bug has zero labels and no maintainer comment — the only follow-up is ~jgneff in 2023 describing the same socket error on s390x Launchpad builds (openjdk-beta +build/2183753), so it has never been categorised here. Scope is outside snapcraft's code: grep for 'snapd.socket' across the repo returns no matches, the reporter confirms 'snapcraft-ing works normally', and the GitHub twin canonical/snapcraft#1837 was closed as off-topic with the maintainer redirecting to this Launchpad bug. It needs a maintainer to confirm the report belongs to snapd/environment support rather than snapcraft, but the 2018 Codenvy 5.22.0 / Ubuntu 16.04 environment is no longer easily reproducible, which is why actionability and confidence stay moderate.

Evaluated by: mr-cal-bot

Impact: 25 Quick Win: 4 Complexity: 55 Confidence: 70 Actionability: 35

Issue body

I am running snapd on Codenvy 5.22.0 in a Ubuntu 16.04.3 LTS workspace. Codenvy is based off of Eclipse Che. When I try to run sudo snap install my-snap-name_0.1_amd64.snap --devmode --dangerous I get the error error: cannot communicate with server: Post http://localhost/v2/snaps: dial unix /run/snapd.socket: connect: no such file or directory snapcraft-ing works normally, but I can't install them using snap install

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 25
Quick Win: 4
Complexity: 55
Confidence: 70
Actionability: 35
needs triage snap install fails in a Codenvy (Eclipse Che) container workspace: /run/snapd.socket missing so snapd is unreachable, while snapcraft itself builds fine. No maintainer response; still open, later user reports the same error on s390x Launchpad builds.
stealth/space-bunny-alpha
Impact: 12
Quick Win: 1
Complexity: 65
Confidence: 82
Actionability: 15
close not a bug snapd not running inside Codenvy/Eclipse Che containers (missing /run/snapd.socket) so `snap install` fails; snapcraft builds fine. Closed as off-topic and redirected to Launchpad #1740851.
qwen/qwen3.6-35b-a3b
Impact: 10
Quick Win: 7
Complexity: 10
Confidence: 95
Actionability: 80
close not a bug User unable to run snapd in Codenvy workspace; issue closed and redirected to Launchpad as it concerns snapd, not snapcraft.
qwen/qwen3.8-27b
Impact: 10
Quick Win: 7
Staleness: 90
Complexity: 30
Confidence: 80
Support Request: 70
close not a bug User reports snapd socket missing in a Codenvy 5.22.0 workspace, so snap install fails with 'cannot communicate with server'. Issue was closed and redirected to Launchpad (snapd tracker); the environment problem remains unresolved. No comments, last activity ~3 years ago.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 15
Confidence: 95
Support Request: 95
close not a bug User reports missing snapd socket when installing snaps in an outdated Codenvy workspace on Ubuntu 16.04. No maintainer response. Environment is long deprecated.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 15
Confidence: 90
Support Request: 85
close stale User reports snapd socket connection errors in Codenvy 5.22.0 on Ubuntu 16.04. Issue lacks maintainer response, targets EOL OS and obsolete IDE, and has been inactive for years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 15
Confidence: 90
Support Request: 85
close stale Reports missing snapd socket error when installing snaps in a Codenvy 5.22.0 workspace on Ubuntu 16.04. No maintainer interaction. Environment and OS are long deprecated.

Update history

Date Change
created

Related work

  • Duplicate Of: canonical/snapcraft#1837 (confidence 85%)

    Same title and report on GitHub; closed as off-topic with the maintainer redirecting reporters to this Launchpad bug.

  • Related To: snapcraft (launchpad)#2072436 (confidence 70%)

    Untitled-similar Launchpad bug with the same 'cannot communicate with server ... /run/snapd.socket' error, also open and untriaged.

Related issues

Issue Project State Summary Similarity
#1837 Can't run snapd on Codenvy 5.22.0 snapcraft closed Off-topic report: snapd could not run inside Codenvy (Eclipse Che) workspaces. Maintainer redirected to Launchpad and closed; Launchpad bug 1740851 was still open when reviewed.
86%