← Back to issue list

Rebuilding a Go project results in error "error obtaining VCS status" in privileged containers

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#2004544
Type
issue
State
open
Author
~saviq
Labels
—
Created
Updated
Closed
—

Current evaluation

Go rebuilds in privileged LXD fail with Git dubious-ownership errors from mixed host/container ownership; this duplicates #1990298 and is addressed by craft-providers 1.7.2.

Suggested action: close resolved

Reason: The maintainer reproduced the failure with security.privileged=true and showed git status --porcelain failing because .git was owned by UID 1000 while the build ran as root. The fix landed in commit 9ab9a75dc, updating craft-providers to 1.7.2 in PR #4032; the reporter also explicitly identified #1990298 as the same LXD ownership failure.

Evaluated by: mr-cal-bot

Impact: 43 Quick Win: 20 Complexity: 50 Confidence: 84 Actionability: 92

Issue body

Having built a Go snap from a Git repo, rebuilding it results in breakage that only cleaning helps with: $ snapcraft --use-lxd # builds fine # change source $ snapcraft --use-lxd Updating build step for spread ('pull' step changed) + snapcraftctl build + go mod download + go install -p 16 -ldflags -linkmode=external ./... error obtaining VCS status: exit status 128 Use -buildvcs=false to disable VCS stamping. error obtaining VCS status: exit status 128 Use -buildvcs=false to disable VCS stamping.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 43
Quick Win: 20
Complexity: 50
Confidence: 84
Actionability: 92
close resolved Go rebuilds in privileged LXD fail with Git dubious-ownership errors from mixed host/container ownership; this duplicates #1990298 and is addressed by craft-providers 1.7.2.
stealth/space-bunny-alpha
Impact: 40
Quick Win: 17
Complexity: 43
Confidence: 91
Actionability: 76
keep open Go rebuilds in privileged LXD containers fail VCS stamping due to mixed .git ownership; maintainers reproduced it, but no fix is evidenced and a duplicate was linked.
stealth/space-bunny-alpha
Impact: 48
Quick Win: 17
Complexity: 50
Confidence: 89
Actionability: 72
needs triage Untriaged Go/LXD rebuild failure reports "error obtaining VCS status" (exit 128) after source changes; cleaning works, but the underlying Git error and Snapcraft version are missing.
qwen3.6-35b-a3b-mtp-q6
Impact: 50
Quick Win: 32
Staleness: 95
Complexity: 35
Confidence: 35
Support Request: 15
needs triage Rebuilding a Go snap in LXD fails with VCS status error; unlabelled, no maintainer response, 1309 days old
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 30
Confidence: 90
Support Request: 20
needs triage Go snap rebuild in LXD fails with VCS status error. Issue lacks labels, maintainer response, or comments after over three years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 35
Confidence: 90
Support Request: 20
needs triage Rebuilding a Go snap in LXD fails with a VCS status error. Unlabeled, unassigned, zero maintainer comments, and inactive for over three years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 10
Confidence: 80
Support Request: 90
needs triage Go snap rebuild fails with VCS status error in LXD. Unlabelled, zero comments, inactive for over three years, awaiting maintainer assessment.

Update history

Date Change
created

Related work

  • Duplicate Of: snapcraft (launchpad)#1990298 (confidence 90%)

    The reporter explicitly called this a duplicate, and both reports involve Git dubious-ownership failures in LXD builds.

  • Likely Fixed By: snapcraft#4032 (confidence 84%)

    Commit 9ab9a75dc updates craft-providers to 1.7.2, matching the recorded fix for the related LXD ownership problem.

Related issues

No related issues found above the similarity threshold.