chore(deps): update dependency containers/automation_images to v20240102

[renovate]

This PR contains the following updates:

Package	Update	Change
containers/automation_images	major	20231208t193858z-f39f38d13 -> 20240102t155643z-f39f38d13

---

Release Notes

containers/automation_images (containers/automation_images)

v20240102t155643z-f39f38d13

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[edsantiago]

The error I see is:

Get "https://busybox.net/downloads/binaries/1.31.0-i686-uclibc/busybox": net/http: TLS handshake timeout

...which smells like a flake but I don't seem to have rerun privs on this repo.

[cevich]

Added privs for @edsantiago

[edsantiago]

This is failing consistently.

[cevich]

Something weird is going on. When I curl -O from that URL, it works fine.

IIRC github-actions workflows run from the Azure cloud. Maybe they're having some kind of networking outage?

[edsantiago]

Your last retry succeeded!
/lgtm

[cevich]

Your last retry succeeded!

Great, so maybe just some odd networking hiccup then. IMHO, Azure is the least reliable of the major cloud providers. I'm not THAT surprised something like this randomly broke. It could also easily be a problem on the CDN-side, those occasionally flake as well. All speculation of course.

There have been a few cases on CI jobs over the past months, where a github-actions workflow (they run in Azure) had a networking failure to git clone FROM GITHUB! That's both embarrassing (for them) and hilarious (for me).