Files
my-docs/.github/workflows/buidl_and_push_ghcr.yml
gitea_admin 5cf886cc5f
Some checks failed
Docker Image CI / build-and-push (push) Failing after 8s
更新 .github/workflows/buidl_and_push_ghcr.yml
2025-12-18 06:23:31 +00:00

67 lines
2.2 KiB
YAML

name: Docker Image CI
on:
workflow_dispatch:
push:
branches:
- main
jobs:
build-and-push:
runs-on: ubuntu-latest
# 不要在 rootless 环境下使用 container: ...
steps:
- name: Checkout code
uses: actions/checkout@v4
with:
fetch-depth: 0
# 1. 提取变量步骤保持不变,这很有用
- name: Get Meta
id: meta
run: |
# 【修改点】不要自动抓取,直接写死你的外部 HTTPS 域名 (不带 https://)
# 例如: git.example.com
REGISTRY_HOST="gitea.173114.xyz"
REPO_LOWER=$(echo "${{ gitea.repository }}" | tr '[:upper:]' '[:lower:]')
SHA_SHORT=$(git rev-parse --short HEAD)
echo "REGISTRY_HOST=$REGISTRY_HOST" >> $GITHUB_OUTPUT
echo "IMAGE_NAME=$REPO_LOWER" >> $GITHUB_OUTPUT
echo "VERSION_SHA=$SHA_SHORT" >> $GITHUB_OUTPUT
# 打印一下,方便调试
echo "Will build: $REGISTRY_HOST/$REPO_LOWER:$SHA_SHORT"
# 2. 登录步骤 (Login Action 通常没问题,它只写配置文件)
- name: Log in to Gitea Registry
uses: docker/login-action@v3
with:
registry: ${{ steps.meta.outputs.REGISTRY_HOST }}
username: ${{ gitea.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
# 3. 【核心修改】使用原生 Shell 命令替代 setup-buildx 和 build-push-action
# 这样直接使用 runner 宿主机的 docker 客户端,绕过 JS 库的连接 bug
- name: Build and Push (Native)
env:
REGISTRY: ${{ steps.meta.outputs.REGISTRY_HOST }}
IMAGE: ${{ steps.meta.outputs.IMAGE_NAME }}
TAG_LATEST: latest
TAG_SHA: ${{ steps.meta.outputs.VERSION_SHA }}
run: |
FULL_IMAGE_NAME="$REGISTRY/$IMAGE"
echo "Building $FULL_IMAGE_NAME..."
# 直接使用 docker build
docker build . \
--file Dockerfile \
--tag "$FULL_IMAGE_NAME:$TAG_LATEST" \
--tag "$FULL_IMAGE_NAME:$TAG_SHA"
echo "Pushing images..."
docker push "$FULL_IMAGE_NAME:$TAG_LATEST"
docker push "$FULL_IMAGE_NAME:$TAG_SHA"