Improve documentation for workspace ownership mismatches #3284
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.
Git requires that a repository directory be owned by the user executing
git
. In the normal case, it will print a messagewhich is easily searchable online, but unfortunately
git config
does not print such a nice message, and simply printswhich is misleading and hard to diagnose.
This came up for us when running Scala Steward as a AWS Fargate task using AWS EFS as its persistent storage. We configured the task to mount the EFS volume using UID 1001, which is the default UID for sbt-native-packager Docker containers, but in fact, Scala Steward current runs as root (#3283). While looking into the issue, we noticed that the article titled Running scala-steward periodically on AWS Fargate no longer exists, so this PR also removes that link from the documentation. (Hopefully we'll be able to publish some details about how we're running Scala Steward using Fargate as a replacement!)