Build Push Action Context Deadline Exceeded

[olzemal]

Describe the bug
After increasing the Build & Push Action timeout to 20 minutes we now run into a different error with builds timing out. We have to investigate deeper.

To Reproduce
https://github.com/opendefensecloud/solution-arsenal/actions/runs/22891590081/job/66415824409?pr=220#step:7:795

Error: buildx failed with: ERROR: failed to build: failed to solve: DeadlineExceeded: failed to push ghcr.io/opendefensecloud/solar-apiserver:pr-220: no active session for r8bj6g788t6jmovou7s4fh0bq: context deadline exceeded

Expected behavior
The build and push process does not timeout / cancels context too early.

[olzemal]

Noticed this in #220. We should probably wait with #229 and #227

[olzemal]

I updated our github action runner -> https://gitlab.opencode.de/bwi/ace/hcloud/-/merge_requests/1

We are using a custom image for github actions, so i need to first update that. -> opendefensecloud/github-actions-runner#18

[olzemal]

Adding resource requests explicitly -> https://gitlab.opencode.de/bwi/ace/hcloud/-/merge_requests/2

[olzemal]

New error, maybe a networking issue in the cluster

https://github.com/opendefensecloud/solution-arsenal/actions/runs/22911655161/job/66485471494?pr=265#step:6:36

Error: Error response from daemon: Get "https://ghcr.io/v2/": Get "https://ghcr.io/token?account=olzemal&client_id=docker&offline_token=true&service=ghcr.io": net/http: request canceled (Client.Timeout exceeded while awaiting headers) (Client.Timeout exceeded while awaiting headers)

[olzemal]

I noticed that #265 probably intoduced a bug to the images pushed to ghcr:

$ docker pull ghcr.io/opendefensecloud/solar-apiserver:pr-265
pr-265: Pulling from opendefensecloud/solar-apiserver
no matching manifest for linux/amd64 in the manifest list entries