melabidi/carmanagement
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

build fix 13
Build & Deploy / Build & Push Docker Image (push) Successful in 5m47s
Details
Build & Deploy / Deploy to VPS (push) Failing after 21s
Details

Browse Source
This commit is contained in:
root
2026-07-04 16:38:28 -04:00
parent d238e6e806
commit e1b848042b
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/build-and-deploy.yml
+1 -1
View File
@@ -14,7 +14,7 @@ env:
# TODO: Remove after installing internal CA certificate on the runner
GIT_SSL_NO_VERIFY: "true"
REGISTRY_HOST: 192.168.3.80
DEPLOY_REGISTRY_HOST: 192.168.3.80
DEPLOY_REGISTRY_HOST: 10.0.0.4
DEPLOY_SSH_HOST: 10.0.0.1
DOCKERFILE_PATH: Dockerfile.production
DOCKER_PLATFORM: linux/amd64
docs/DOCKER.md
+3 -3
View File
@@ -407,11 +407,11 @@ Expected response:
HTTP/1.1 401 Unauthorized
```
If CI uses the Gitea container registry, `REGISTRY_HOST` and `DEPLOY_REGISTRY_HOST` in `.gitea/workflows/build-and-deploy.yml` should point at the Gitea registry host, for example `192.168.3.80`. From the VPS build host, verify Docker can reach it:
If CI uses the Gitea container registry, `DEPLOY_REGISTRY_HOST` in `.gitea/workflows/build-and-deploy.yml` must be the address the VPS can use to reach Gitea. In the VPN setup, use the Gitea VPN IP `10.0.0.4`, not the LAN IP `192.168.3.80`. From the VPS build host, verify Docker can reach it:
```bash
curl -vk https://192.168.3.80/v2/
docker login 192.168.3.80
curl -vk https://10.0.0.4/v2/
docker login 10.0.0.4
```
If `curl` times out, fix network routing or firewall access from the VPS to the Gitea server before rerunning CI. If Docker reports a certificate error, install the Gitea registry CA certificate on the VPS Docker host or configure Docker for that internal registry according to your environment.