Updating base golang image

[pjohnst5]

Just updating the base golang image again

I'm curious:

• Is it preferential that I do this in a separate PR every time? (to keep PRs scoped to just 1 thing)
• Are there any automations to do this sort of thing like dependabot does?

[Copilot]

Pull Request Overview

This PR updates the base golang Docker image across the project by changing the SHA256 hash reference to point to a newer version of the Microsoft golang image.

• Updates golang base image SHA256 hash from 7d33a8015c48c06e97ecd5139181594b550d4d4d6a9d7fb19083192541213753 to 1c631a31ac7684cf03c7d2dab9b69b06f15f89177baba51421479d29df22177c

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
cns/Dockerfile	Updates golang base image SHA256 hash for CNS component
cni/Dockerfile	Updates golang base image SHA256 hash for CNI component

Comments suppressed due to low confidence (2)

cns/Dockerfile:8

• The SHA256 hash 1c631a31ac7684cf03c7d2dab9b69b06f15f89177baba51421479d29df22177c appears to be incomplete. Docker image SHA256 hashes should be 64 characters long, but this hash is only 63 characters. Please verify the correct hash for the golang image.

FROM --platform=linux/${ARCH} mcr.microsoft.com/oss/go/microsoft/golang@sha256:1c631a31ac7684cf03c7d2dab9b69b06f15f89177baba51421479d29df22177c AS go

cni/Dockerfile:9

• The SHA256 hash 1c631a31ac7684cf03c7d2dab9b69b06f15f89177baba51421479d29df22177c appears to be incomplete. Docker image SHA256 hashes should be 64 characters long, but this hash is only 63 characters. Please verify the correct hash for the golang image.

FROM --platform=linux/${ARCH} mcr.microsoft.com/oss/go/microsoft/golang@sha256:1c631a31ac7684cf03c7d2dab9b69b06f15f89177baba51421479d29df22177c AS go

[pjohnst5]

The reason i do these separately, is let's say I lump it into #3878

Then if we need to revert #3878, the base golang change would also be reverted

So I like to separate them just in case, but also curious others' points of view

[pjohnst5]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[pjohnst5]

@jpayne3506 would you be able to review this for me please? 🙏🏻

[jpayne3506]

@rbtr This looks to be consistent pain point for people. IMO, I would want this to be updated before every release, but I also don't want this to be put onto every PR as it would impact backports ect.

Are there any automations to do this sort of thing like dependabot does?

I have seen solutions with Renovate, but I don't believe dependabot updates we have not been using dependabot correctly for our dockerfiles. We can test it out with a follow on PR.

• relevant thread Updating Dockerfiles within a monorepo dependabot/dependabot-core#9120
• https://github.com/Azure/azure-container-networking/network/updates/17351297/jobs

[rbtr]

it's not a blocking check

[pjohnst5]

@rbtr would you be willing to approve this one?