concourse / concourse/git-resource
detected dubious ownership in repository at '/tmp/build/get'
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 203
- Forks
- 305
- Avg merge
- 11d 14h
- Merged PRs (30d)
- 2
Description
Describe the bug
When attempting to get a git-resource, we receive the git error detected dubious ownership instead of pulling the source code.
Reproduction steps
-
Deploy concourse quickstart using provided docker-compose.yml (using Concourse 7.9.1)
-
Deploy a simple pipeline:
resources:
- name: git-repo
type: git
icon: git
source:
uri: http://gitea:3000/org1/myproject
username: ((gitea.username))
password: ((gitea.password))
jobs:
- name: validate-repo
plan:
- get: git-repo
trigger: false
- task: list-files
config:
inputs:
- name: git-repo
platform: linux
image_resource:
type: registry-image
source:
repository: busybox
run:
path: tree
- Unpause the pipeline
- Receive the following error:
selected worker: 31354ca107d3
Cloning into '/tmp/build/get'...
fatal: detected dubious ownership in repository at '/tmp/build/get'
To add an exception for this directory, call:
git config --global --add safe.directory /tmp/build/get
...
Expected behavior
Expect the git repo to be available for pipeline consumption,
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the Concourse quickstart docker-compose.yml and the pipeline shown, then inspect the git-resource behavior around cloning into /tmp/build/get. Confirm the change by running the same get step and verifying that the repository is available to the pipeline without the dubious-ownership error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100