Felix FaerberandClaude Opus 5
70786f73ab
Docker / build (push) Failing after 17s
Second build failed the same way: docker login to this instance's registry returns "unauthorized" for the automatic Actions token, and declaring permissions: packages: write did not change it -- Gitea's task token is accepted by the API but not by the package registry. So the push uses REGISTRY_TOKEN, an org secret holding a personal access token scoped to write:package and nothing else. The step fails with that sentence in the log rather than another bare "unauthorized", because the difference between a missing secret and a rejected credential is not visible from the error docker prints. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CYFnHida4AdiNDek2pzgXx
70 lines
2.8 KiB
YAML
70 lines
2.8 KiB
YAML
name: Docker
|
|
# Builds the frontend for the HOMELAB instance and pushes it to this Gitea's
|
|
# registry.
|
|
#
|
|
# Read the build args before changing anything: Vite inlines import.meta.env at
|
|
# BUILD time, so VITE_API_URL is baked into the bundle and an image is tied to
|
|
# one API. The GitHub build bakes https://api.t4t-gateway.com -- running that
|
|
# image here would serve a UI at t4tgw.ffaerber.duckdns.org that talks to the
|
|
# VPS, so a test signup would create a real account on production. This build
|
|
# bakes the homelab API instead, which is the whole reason the two instances can
|
|
# run side by side and mean anything.
|
|
#
|
|
# VITE_GOOGLE_CLIENT_ID comes from a repo secret; unset, Google sign-in is the
|
|
# only thing that breaks, and the rest of the instance still exercises.
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
pull_request:
|
|
workflow_dispatch:
|
|
|
|
env:
|
|
HOMELAB_API_URL: https://t4tgw-api.ffaerber.duckdns.org
|
|
|
|
jobs:
|
|
build:
|
|
runs-on: ci-runner
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
|
|
- name: Build
|
|
run: |
|
|
set -eu
|
|
SHA=$(echo "${{ github.sha }}" | cut -c1-7)
|
|
echo "IMAGE=git.ffaerber.duckdns.org/token-for-token/hosted-gateway-frontend" >> "$GITHUB_ENV"
|
|
echo "SHA=$SHA" >> "$GITHUB_ENV"
|
|
docker build \
|
|
--build-arg VITE_API_URL="$HOMELAB_API_URL" \
|
|
--build-arg VITE_GOOGLE_CLIENT_ID="${{ secrets.VITE_GOOGLE_CLIENT_ID }}" \
|
|
--build-arg VITE_COMMIT_SHA=${{ github.sha }} \
|
|
-t "git.ffaerber.duckdns.org/token-for-token/hosted-gateway-frontend:$SHA" .
|
|
|
|
- name: Push
|
|
if: github.event_name != 'pull_request'
|
|
run: |
|
|
set -eu
|
|
# Not the automatic Actions token: this Gitea's package registry rejects
|
|
# it (docker login returns a bare "unauthorized"), with or without a
|
|
# permissions: packages: write block. REGISTRY_TOKEN is an org secret
|
|
# holding a personal access token scoped to write:package only.
|
|
if [ -z "${{ secrets.REGISTRY_TOKEN }}" ]; then
|
|
echo "REGISTRY_TOKEN is not set — create a token with the write:package scope" >&2
|
|
echo "and add it as an org secret on token-for-token. The image built fine;" >&2
|
|
echo "only the push needs it." >&2
|
|
exit 1
|
|
fi
|
|
echo "${{ secrets.REGISTRY_TOKEN }}" | docker login git.ffaerber.duckdns.org -u "${{ vars.REGISTRY_USER || 'ffaerber' }}" --password-stdin
|
|
docker tag "$IMAGE:$SHA" "$IMAGE:latest"
|
|
docker push "$IMAGE:$SHA"
|
|
docker push "$IMAGE:latest"
|
|
docker logout git.ffaerber.duckdns.org
|
|
{
|
|
echo "### Pushed"
|
|
echo
|
|
echo '```'
|
|
echo "$IMAGE:$SHA"
|
|
echo '```'
|
|
echo
|
|
echo "API baked in: $HOMELAB_API_URL"
|
|
} >> "$GITHUB_STEP_SUMMARY"
|