68 lines
1.7 KiB
Markdown
68 lines
1.7 KiB
Markdown
# Remote Gateway Fix (RTX 2080Ti)
|
|
|
|
## Observed on 2026-03-10
|
|
|
|
`memory-gateway` health is up, but `memory/status` and `memory/search` fail with:
|
|
|
|
- `fatal: '/data/memory-repo' does not appear to be a git repository`
|
|
|
|
This means container-side `GIT_REMOTE_URL=/data/memory-repo` is configured,
|
|
but `/data/memory-repo` is not mounted as a valid Git repo.
|
|
|
|
## Fix Steps (run on RTX host)
|
|
|
|
1. Go to project root:
|
|
|
|
```bash
|
|
cd /home/lingyuzeng/project/qmd-local
|
|
```
|
|
|
|
2. Ensure memory repo exists and is a git repo:
|
|
|
|
```bash
|
|
ls -la /home/lingyuzeng/project/qmd-local/qmd-docker-http-mcp/memory-repo/.git
|
|
```
|
|
|
|
3. Add bind mount in `docker-compose.yml` for `memory-gateway` service:
|
|
|
|
```yaml
|
|
services:
|
|
memory-gateway:
|
|
volumes:
|
|
- ./data:/data
|
|
- ./models:/models
|
|
- ./qmd-docker-http-mcp/memory-repo:/data/memory-repo:ro
|
|
```
|
|
|
|
4. Ensure `.env` includes:
|
|
|
|
```bash
|
|
GIT_REMOTE_URL=/data/memory-repo
|
|
```
|
|
|
|
5. Restart services:
|
|
|
|
```bash
|
|
docker compose up -d --build qmd memory-gateway
|
|
```
|
|
|
|
6. Validate:
|
|
|
|
```bash
|
|
curl -fsS http://127.0.0.1:8787/health
|
|
curl -fsS -X POST http://127.0.0.1:8787/memory/status \
|
|
-H 'content-type: application/json' \
|
|
-d '{"branch":"main","require_latest":true}'
|
|
curl -fsS -X POST http://127.0.0.1:8787/memory/search \
|
|
-H 'content-type: application/json' \
|
|
-d '{"branch":"main","query":"OpenClaw","query_type":"search","require_latest":true,"n":5}'
|
|
```
|
|
|
|
## Optional: use Gitea as remote truth source
|
|
|
|
If you want remote gateway to follow Gitea instead of local path:
|
|
|
|
- set `GIT_REMOTE_URL=https://gitea.jmsu.top/lingyuzeng/collective-memory-repo.git`
|
|
- configure auth (token/SSH) inside container
|
|
- restart gateway and validate `memory/status` shows indexed-visible.
|