Replies: 2 comments
-
Could you take a look at #263 , particularly #263 (comment) to see if that might help you get past the chown issue? |
Beta Was this translation helpful? Give feedback.
0 replies
-
From what I understand, the issue is that the mounted directory needs to have the same owner (ID) in the container and on the host. # in $HOME/sourcebot
sudo chown -R 70:70 . # this changes the owner to _www:_www for that directory (ID: 70)
# start container
docker run \
-p 3000:3000 \
--pull=always \
--rm \
-v $(pwd):/data \
-e CONFIG_PATH=/data/config.json \
--name sourcebot \
ghcr.io/sourcebot-dev/sourcebot:latest
latest: Pulling from sourcebot-dev/sourcebot
Digest: sha256:8f5dc35de2fa16426cffb16437cb18336beb1d0a14b5c4bd3b354184962f3c49
Status: Image is up to date for ghcr.io/sourcebot-dev/sourcebot:latest
[Info] Sourcebot version: v4.6.3
[Warning] SOURCEBOT_ENCRYPTION_KEY is not set.
[Info] Loading environment variables from /data/.sourcebot/.secret
[Warning] AUTH_SECRET is not set.
[Info] Loading environment variables from /data/.sourcebot/.authjs-secret
[Warning] AUTH_URL is not set.
./entrypoint.sh: line 132: can't create /data/.sourcebot/.installedv3: Permission denied And the container stops. So I can't run the db init script from within the container, as suggested in #263. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I tried to run sourcebot as docker container, as described in the deployment guide. However, I cannot get it running.
Can someone help me please?
Beta Was this translation helpful? Give feedback.
All reactions