chore: Update docker user mapping for weaver#2140
Open
kaylareopelle wants to merge 1 commit into
Open
Conversation
When we tried to use renovate to update the semantic conventions gem
we encountered the following error:
× Writing of the generated code /output/./lib/opentelemetry/semconv/
│ aspnetcore/metrics.rb failed: Permission denied (os error 13)
This is because the Docker runner's user is different from the user in
the weaver process.
Weaver has a docker guide that recommends setting the user to
$(id -u ${USER}):$(id -g ${USER})
kaylareopelle
requested review from
ahayworth,
arielvalentin,
dazuma,
ericmustin,
fbogsany,
mwear,
plantfansam,
robbkidd,
robertlaurin and
xuan-cao-swi
as code owners
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When we tried to use renovate to update the semantic conventions gem we encountered the following error:
This is because the Docker runner's user is different from the user in the weaver process.
Weaver has a docker guide that recommends setting the user to:
$(id -u ${USER}):$(id -g ${USER})See failure: https://github.com/open-telemetry/opentelemetry-ruby/actions/runs/25760086248/job/75658668044?pr=2136
There are a few other recommendations in the docker guide we can consider adopting if this doesn't solve the problem.