added Dockerfile and adapted build.yaml
Some checks failed
.NET Docker Build & Push / build_and_push (push) Failing after 3m53s
Some checks failed
.NET Docker Build & Push / build_and_push (push) Failing after 3m53s
This commit is contained in:
@@ -1,45 +1,47 @@
|
||||
name: Docker Image Build & Push
|
||||
name: .NET Docker Build & Push
|
||||
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- 'main' # Baut bei jedem Commit auf main
|
||||
- 'main'
|
||||
release:
|
||||
types: [published] # Baut bei jedem neuen Release
|
||||
types: [published]
|
||||
|
||||
jobs:
|
||||
push_to_registry:
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
packages: write
|
||||
contents: read
|
||||
build_and_push:
|
||||
runs-on: ubuntu-latest # Dein Runner mappt das ja auf Debian Bookworm
|
||||
container:
|
||||
image: catthehacker/ubuntu:act-latest # Optional, Standard-Umgebung für den Job selbst
|
||||
|
||||
steps:
|
||||
- name: Check out the repo
|
||||
uses: actions/checkout@v4
|
||||
|
||||
# 1. Login in die Gitea Container Registry
|
||||
# Login in deine Gitea Registry
|
||||
- name: Log in to the Container registry
|
||||
uses: docker/login-action@v3
|
||||
with:
|
||||
registry: gitea.penry.de # <-- HIER DEINE GITEA URL ANPASSEN (ohne https://)
|
||||
registry: gitea.penry.de # <-- ANPASSEN (ohne https://)
|
||||
username: ${{ github.actor }}
|
||||
password: ${{ secrets.GITHUB_TOKEN }}
|
||||
|
||||
# 2. Metadaten extrahieren (Das ist der magische Teil)
|
||||
# Er sorgt dafür, dass bei einem Commit das Tag "main" oder "latest" genutzt wird
|
||||
# und bei einem Release das Tag "v1.2.3"
|
||||
- name: Extract metadata (tags, labels) for Docker
|
||||
# Metadaten (Tags generieren: latest, v1.0, etc.)
|
||||
- name: Extract metadata for Docker
|
||||
id: meta
|
||||
uses: docker/metadata-action@v5
|
||||
with:
|
||||
images: gitea.penry.de/${{ github.repository }}
|
||||
images: gitea.penry.de/${{ github.repository }} # <-- ANPASSEN
|
||||
|
||||
# 3. Bauen und Pushen
|
||||
# Der eigentliche Build.
|
||||
# Da wir ein Multi-Stage Dockerfile haben, führt dieser Schritt
|
||||
# automatisch "dotnet restore" und "dotnet publish" aus.
|
||||
- name: Build and push Docker image
|
||||
uses: docker/build-push-action@v5
|
||||
with:
|
||||
context: .
|
||||
file: ./Dockerfile
|
||||
push: true
|
||||
tags: ${{ steps.meta.outputs.tags }}
|
||||
labels: ${{ steps.meta.outputs.labels }}
|
||||
labels: ${{ steps.meta.outputs.labels }}
|
||||
# Wichtig für Raspberry Pi Builds, falls du Cross-Platform bauen willst (optional)
|
||||
platforms: linux/arm64
|
||||
Reference in New Issue
Block a user