← Back to issue list

Service "snapcraft" stopped unexpectedly with code 70

View original Github issue

Metadata

Project
snapcraft-rocks
Number
#57
Type
issue
State
open
Author
abitrolly
Labels
—
Created
Updated
Closed
—

Current evaluation

Snapcraft OCI image pebble service exits with code 70. Debugging revealed leftover build artifacts in the mounted project dir as the cause; user resolved it by cleaning up and setting SNAPCRAFT_BUILD_ENVIRONMENT=host. Follow-ups filed as #58-#60. Still open, unlabelled.

Suggested action: close not a bug

Reason: The reporter confirmed the image works after removing leftover build artifacts (parts/prime/snap/stage and the stale .snap) and setting SNAPCRAFT_BUILD_ENVIRONMENT=host, so the reported failure was a user-environment issue, not an image bug. The remaining improvement asks (better error messages, env vars in the image, WORKDIR) were explicitly split into follow-up issues #58, #59, and #60, which are still open and unlabelled, so nothing actionable is left in this issue itself.

Impact: 15 Quick Win: 10.5 Staleness: 80 Complexity: 30 Confidence: 80 Support Request: 70

Issue body

OCI image doesn't work for me. ```sh $ podman run -it --rm --security-opt label=disable -v `pwd`:/project ghcr.io/canonical/snapcraft:8_core24 pack 2024-09-24T10:25:11.058Z [pebble] Started daemon. 2024-09-24T10:25:11.059Z [pebble] POST /v1/services 1.011861ms 202 2024-09-24T10:25:11.060Z [pebble] Service "snapcraft" starting: /bin/run-snapcraft.sh [ pack ] 2024-09-24T10:25:12.062Z [pebble] GET /v1/changes/1/wait 1.002295243s 200 2024-09-24T10:25:12.063Z [pebble] Started default services with change 1. 2024-09-24T10:25:25.960Z [pebble] Service "snapcraft" stopped unexpectedly with code 70 2024-09-24T10:25:25.960Z [pebble] Service "snapcraft" on-failure action is "shutdown", triggering failure shutdown 2024-09-24T10:25:25.960Z [pebble] Server exiting! Reason: <nil> ``` Is it possible to get more specific error message?

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 15
Quick Win: 10.5
Staleness: 80
Complexity: 30
Confidence: 80
Support Request: 70
close not a bug Snapcraft OCI image pebble service exits with code 70. Debugging revealed leftover build artifacts in the mounted project dir as the cause; user resolved it by cleaning up and setting SNAPCRAFT_BUILD_ENVIRONMENT=host. Follow-ups filed as #58-#60. Still open, unlabelled.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 15
Confidence: 90
Support Request: 85
close stale User reports snapcraft container service failing with code 70. Maintainer assists with debugging, revealing missing environment variables and leftover build artifacts causing conflicts. Issue resolved by user cleanup and configuration adjustments.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 10
Confidence: 85
Support Request: 85
close stale User reported snapcraft OCI image failing with exit code 70. Resolved by author after cleaning leftover build artifacts and setting required environment variables. Issue is stale and resolved.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 30
Confidence: 90
Support Request: 20
close stale Snapcraft OCI image exits with code 70 due to unhelpful error messages and leftover build artifacts causing YAML parse failures. Resolved via workarounds; author opened related PRs to improve container environment setup and error handling.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft-rocks#58 (confidence 95%)

    Explicitly opened by the reporter in this issue to catch issues with older/invalid YAML files; still open.

  • Related To: snapcraft-rocks#59 (confidence 95%)

    Explicitly opened by the reporter to add SNAPCRAFT_BUILD_ENVIRONMENT=host at the Docker level; still open.

  • Related To: snapcraft-rocks#60 (confidence 95%)

    Explicitly opened by the reporter to set WORKDIR to /workdir at the Docker level; still open.

Related issues

No related issues found above the similarity threshold.