From e1b848042b5859800c427c8fd2e276b19f25f22d Mon Sep 17 00:00:00 2001 From: root Date: Sat, 4 Jul 2026 16:38:28 -0400 Subject: [PATCH] build fix 13 --- .gitea/workflows/build-and-deploy.yml | 2 +- docs/DOCKER.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.gitea/workflows/build-and-deploy.yml b/.gitea/workflows/build-and-deploy.yml index 49df015..194ee08 100644 --- a/.gitea/workflows/build-and-deploy.yml +++ b/.gitea/workflows/build-and-deploy.yml @@ -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 diff --git a/docs/DOCKER.md b/docs/DOCKER.md index a3a3da3..12d8ae2 100644 --- a/docs/DOCKER.md +++ b/docs/DOCKER.md @@ -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.