Fix registry hostname (duckdns) and Trivy github auth #4

Merged

willemjan merged 2 commits from dev into main 2026-07-25 20:05:34 +00:00

Conversation 0 Commits 2 Files Changed 2

+12 -8

willemjan commented 2026-07-25 20:04:36 +00:00

Owner

Copy Link

Copy Source

Registry via gitea.zb-kw.duckdns.org (HTTPS, confirmed reachable) i.p.v. gitea.zb.local (plain HTTP) of gitea.zb.lan (nog niet gerouteerd). Fixt ook trivy-action se token-setup-trivy die anders een ongeldig Gitea-token naar github.com stuurt.

Registry via gitea.zb-kw.duckdns.org (HTTPS, confirmed reachable) i.p.v. gitea.zb.local (plain HTTP) of gitea.zb.lan (nog niet gerouteerd). Fixt ook trivy-action se token-setup-trivy die anders een ongeldig Gitea-token naar github.com stuurt.

willemjan added 2 commits 2026-07-25 20:04:36 +00:00

updated sonarqube scan action version d6107515c0

use the working duckdns hostname for the registry, fix trivy github auth ... e0d6b79e68

gitea.zb.local resolves but is plain HTTP, which Docker refuses as a
registry without daemon-level insecure-registry config. gitea.zb.lan
resolves but nothing answers there yet (proxy not configured for it).
gitea.zb-kw.duckdns.org is confirmed reachable end-to-end over HTTPS,
including the registry v2 API, from both the runner and the deploy
target, so use that consistently. Also fix aquasecurity/trivy-action's
token-setup-trivy input, which defaults to gitea.token and gets
rejected by github.com when it tries to clone the install script.

Co-Authored-By: Claude Sonnet 5 <[email protected]>

willemjan merged commit e3443e9f9f into main 2026-07-25 20:05:34 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

No items

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

jenkins renovate-bot willemjan

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: willemjan/glucose-dashboard#4