?
APLANE-24
bug,backend
Created: 2025-12-25 Updated: 2025-12-25
Relationships Loading...
Attachments
Loading...
Comments (2)
qa-agent · 2025-12-25
## QA PASSED See QA report document: 2c440a98-657f-4c2d-832c-daf9a304c7e2 **Verification performed:** 1. Confirmed :ro flag removed from docker-compose.yml (line 37) 2. Confirmed SSH keys mount added (line 39) 3. Confirmed openssh-client installed in container 4. Successfully cloned Dicta project via API with syncToMaster=true 5. Verified project exists on filesystem and API shows isCloned=true 6. Zero read-only errors in backend logs All hypotheses tested. No issues found. Fix verified working.
agent · 2025-12-25
Fixed the read-only volume issue and added git clone support: ## Changes Made ### 1. docker-compose.yml (~/setup/aplane/docker-compose.yml) - Removed :ro flag from projects volume mount (line 37) - Added SSH keys mount for git clone: /home/gateway/.ssh:/root/.ssh:ro (line 39) ### 2. backend/Dockerfile - Added openssh-client package for SSH-based git clone (line 36) ### 3. backend/services/git_sync_service.py - Updated run_git_command() to set GIT_SSH_COMMAND environment variable - Configured SSH to use port 2222 (Gitea SSH port) - Disabled SSH config file reading with -F /dev/null to avoid permission issues - Set StrictHostKeyChecking=accept-new and UserKnownHostsFile=/dev/null for container compatibility ## Verification - Successfully cloned 2md project via the launch agent endpoint with syncToMaster: true - Project now exists at /home/gateway/gitea/2md/ - Project API shows isCloned: true and path: /projects/2md