← 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

OCI builds hid Snapcraft's ConstructorError; verbose mode traced it to stale build directories, whose removal restored the build. Clearer default diagnostics remain open through #58 and #59.

Suggested action: keep open

Reason: Maintainer @tigarmo supplied the image's verbose invocation, which exposed a ConstructorError; the reporter then confirmed that deleting stale parts, prime, snap, and stage directories made packing work. This validates a real diagnostics gap with a workaround, while #58 and #59 isolate narrower follow-up improvements.

Evaluated by: mr-cal-bot

Impact: 42 Quick Win: 18 Complexity: 42 Confidence: 92 Actionability: 74

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
stealth/space-bunny-alpha
Impact: 42
Quick Win: 18
Complexity: 42
Confidence: 92
Actionability: 74
keep open OCI builds hid Snapcraft's ConstructorError; verbose mode traced it to stale build directories, whose removal restored the build. Clearer default diagnostics remain open through #58 and #59.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 13
Complexity: 30
Confidence: 70
Actionability: 60
keep open User reports OCI image fails with code 70 and requests better error messages. Root cause found: leftover build artifacts causing ConstructorError. User opened follow-up issues for improvements.
qwen/qwen3.8-27b
Impact: 15
Quick Win: 10
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.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/snapcraft-rocks#59 (confidence 97%)

    Reporter opened #59 to add SNAPCRAFT_BUILD_ENVIRONMENT=host, which was required for meaningful manual troubleshooting.

  • Related To: canonical/snapcraft-rocks#58 (confidence 94%)

    Reporter opened #58 to validate project YAML before running Snapcraft and catch incompatible files.

  • Related To: canonical/snapcraft-rocks#61 (confidence 70%)

    Commit 4538525 updates verbosity documentation, potentially making the existing verbose-output workaround more discoverable.

Related issues

Issue Project State Summary Similarity
#1609803 snapcraft cleanbuild --no-clean-up snapcraft (launchpad) closed Cleanbuild debugging landed in snapcore/snapcraft PR #740 (commit a24083e75); follow-up PR #1404 made --debug enter a shell when builds fail.
72%
#1675516 can't cleanbuild snapcraft itself snapcraft (launchpad) closed Fresh testing confirmed Snapcraft could build itself successfully; the report was closed after the suspected interim fix was verified.
70%