vrubel/t2sTelegramBot
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix: restore normal docker login+push; dind has insecure-registries via mounted daemon.json
Some checks failed
CI/CD Pipeline / build-and-deploy (push) Failing after 0s
Details

Browse source
This commit is contained in:
vrubel 2026-06-06 22:35:06 +00:00
parent 0f9c67a3b1
commit 550fb6ecbf
1 changed files with 1 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

12
.forgejo/workflows/test.yml
View file

@ -35,17 +35,7 @@ jobs:
run: docker compose down run: docker compose down
- name: Login to Gitea Container Registry - name: Login to Gitea Container Registry
run: | run: echo "${{ secrets.REGISTRY_TOKEN }}" | docker login http://192.168.8.174:3000 -u "${{ secrets.REGISTRY_USER }}" --password-stdin
echo "=== whoami: $(whoami) ==="
echo "=== HOME: $HOME ==="
echo "=== DOCKER_HOST: ${DOCKER_HOST:-unset} ==="
echo "=== docker version ==="
docker --version
echo "=== docker info insecure ==="
docker info 2>&1 | grep -A3 Insecure || echo "no insecure info"
echo "=== attempting login ==="
echo "${{ secrets.REGISTRY_TOKEN }}" | docker login http://192.168.8.174:3000 -u "${{ secrets.REGISTRY_USER }}" --password-stdin 2>&1
echo "=== exit code: $? ==="
- name: Push image to registry - name: Push image to registry
run: docker push 192.168.8.174:3000/vrubel/t2s-telegram-bot:latest run: docker push 192.168.8.174:3000/vrubel/t2s-telegram-bot:latest