From d09921b09bfa7c146cfd49de066745c054dbd7c0 Mon Sep 17 00:00:00 2001 From: NANDO9322 Date: Wed, 21 Jan 2026 21:14:28 -0300 Subject: [PATCH] fix: bypass container image to avoid api version error --- .forgejo/workflows/deploy.yaml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/.forgejo/workflows/deploy.yaml b/.forgejo/workflows/deploy.yaml index e101ee2..427cfc3 100644 --- a/.forgejo/workflows/deploy.yaml +++ b/.forgejo/workflows/deploy.yaml @@ -8,28 +8,29 @@ on: jobs: build-and-deploy: runs-on: self-hosted + # O PULO DO GATO: Definir container como vazio força o uso do host (Zeus) + container: + image: "" steps: - name: Checkout Code uses: actions/checkout@v4 - name: Build and Push Image run: | - # Define o socket do Podman para a sessão + # Usa o socket do Podman que você já ativou export DOCKER_HOST=unix:///run/podman/podman.sock - # Login no seu registro + # Login echo "${{ secrets.FORGEJO_TOKEN }}" | podman login git.saveinmed.com.br -u ${{ github.actor }} --password-stdin - # Build da imagem (usando a pasta backend onde está o Dockerfile) + # Build na pasta backend podman build -t git.saveinmed.com.br/${{ github.repository }}:latest ./backend - # Envio para o registro + # Push podman push git.saveinmed.com.br/${{ github.repository }}:latest - name: Deploy to K3s run: | - # Aplica as configurações no cluster + # Como o kubectl já funciona no Zeus (root), ele vai disparar o deploy kubectl apply -f k8s/ - - # Força a atualização do Pod no Poseidon kubectl rollout restart deployment/photum-backend -n photum