ownership mismatch for local repositories

[cobbzilla]

My config.json is:

{
  "$schema": "https://raw.github.com/sourcebot-dev/sourcebot/main/schemas/v3/index.json",
  "connections": {
    "my-repos": {
      "type": "git",
      "url": "file:///my-repos/*"
    }
  }
}

And I am starting the docker container with:

docker run \
    -p 3000:3000 \
    --pull=always \
    --rm \
    -v $(pwd)/repos:/my-repos:ro \
    -v $(pwd):/data \
    -e CONFIG_PATH=/data/config.json \
    --name sourcebot \
    ghcr.io/sourcebot-dev/sourcebot:latest

But the container has this error, and doesn't seem to have indexed any repositories:

backend] | 2025-07-31T22:00:41.846Z error: [connection-manager] Failed to compile repo data for connection 1 (my-repos): Error: fatal: detected dubious ownership in repository at '/my-repos/repo-name'
[backend] | To add an exception for this directory, call:
[backend] |
[backend] |     git config --global --add safe.directory /my-repos/repo-name
[backend] |
[backend] | 2025-07-31T22:00:41.859Z info: [connection-manager] Connection sync job for connection my-repos (id: 1, jobId: 1) failed with error: BackendException: CONNECTION_SYNC_SYSTEM_ERROR

Everything is owned by the same user (the user who owns the files also invokes docker run). Maybe this is because the docker container is running as root? What's the right way to get the UIDs properly aligned so this works?

[cobbzilla]

Following up, confirm that this config results in a broken deploy. When I visit localhost:3000, I see the welcome screen, but on the "Create Owner Account" screen, whenever I enter an email and password and click "Sign up", it goes back to the first screen "Welcome to Sourcebot". The errors in the server logs are:

[web] | [edge] Sentry was not initialized
[web] | s [Error]: {"statusCode":401,"errorCode":"NOT_AUTHENTICATED","message":"Not authenticated"}
[web] |     at S (/app/packages/web/.next/server/app/[domain]/page.js:1:4743) {
[web] |   serviceError: {
[web] |     statusCode: 401,
[web] |     errorCode: 'NOT_AUTHENTICATED',
[web] |     message: 'Not authenticated'
[web] |   },
[web] |   digest: '3189048776'
[web] | }
[web] | 2025-07-31T22:07:30.156Z info: [login-page] Login page loaded

[web] | [auth][error] CredentialsSignin: Read more at https://errors.authjs.dev#credentialssignin
[web] |     at rX (/app/packages/web/.next/server/chunks/2237.js:497:43290)
[web] |     at async r4 (/app/packages/web/.next/server/chunks/2237.js:497:52491)
[web] |     at async r7 (/app/packages/web/.next/server/chunks/2237.js:497:56802)
[web] |     at async /app/packages/web/.next/server/chunks/6276.js:19:58771
[web] |     at async /app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:38411
[web] |     at async e_.execute (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:27880)
[web] |     at async e_.handle (/app/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:39943)
[web] |     at async doRender (/app/node_modules/next/dist/server/base-server.js:1366:42)
[web] |     at async cacheEntry.responseCache.get.routeKind (/app/node_modules/next/dist/server/base-server.js:1588:28)
[web] |     at async NextNodeServer.renderToResponseWithComponentsImpl (/app/node_modules/next/dist/server/base-server.js:1496:28)
[web] | 2025-07-31T22:08:30.148Z info: [login-page] Login page loaded

[brendan-kellam]

To your first issue, could you see if #168 is relevant to the issue you are running into?

For the second issue: I'm not exactly sure what's going on there.. as a first step, could you wipe all cookies for the site? Additionally, if you are running this in a deployed environment (i.e., not locally on localhost:3000), make sure you set AUTH_URL to the domain of your deployment (e.g., htpps://sourcebot.example.com)

[cobbzilla]

Thank you for these suggestions. Adding a /root/.gitconfig allowed the container to get further, however now I see one of these errors for each of my repositories (redacted for privacy):

[backend] | 2025-08-05T15:39:32.780Z error: [zoekt] 2025/08/05 15:39:32 setTemplatesFromConfig(/repos/<my-repo-name>): unknown git hosting site "ssh+git://git@<my-gitea-hostname>/<project-name>/<my-repo-name>"

I'd like to analyze the local repositories that are already cloned & mounted within the docker container. If I must configure access to the remote git server, I can, but is that really necessary?

[brendan-kellam]

Ah yea I was able to repro this locally with a gitea repo and a similar config as yours, this is a bug. Looks like it's in this method in zoekt: https://github.com/sourcebot-dev/zoekt/blob/12a2f4ad075359a09bd8a91793acb002211217aa/gitindex/index.go#L293.

I'll file a issue to fix this. Besides the error message, it shouldn't impact anything else - the repos should be indexed and searchable.

*Edit: filed the issue here: #434