fix make vendor-check

[shalk]

What this PR does:

Which issue(s) this PR fixes:
Fixes #3905

Checklist

• Tests updated
• Documentation added
• CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

[joe-elliott]

i saw the issue, but i'd prefer to keep using a container to run yacc instead of requiring everyone to install yacc locally.

[shalk]

i saw the issue, but i'd prefer to keep using a container to run yacc instead of requiring everyone to install yacc locally.

I keep the container, and i found the golang version in grafana/loki-build-image:0.21.0 is too low.
loki-build-image 0.33.2 's golang version is 1.22.5
It works.

But I think it is hard to keep the version consistent with loki-build-image. should we use golang:1.22 instead ?

[javiermolinar]

i saw the issue, but i'd prefer to keep using a container to run yacc instead of requiring everyone to install yacc locally.

I keep the container, and i found the golang version in grafana/loki-build-image:0.21.0 is too low. loki-build-image 0.33.2 's golang version is 1.22.5 It works.

But I think it is hard to keep the version consistent with loki-build-image. should we use golang:1.22 instead ?

Maybe Tempo should have it's own build image

[joe-elliott]

loki-build-image 0.33.2 's golang version is 1.22.5
It works.

Let's just update to 0.33.2 if that works.

should we use golang:1.22 instead ?

I honestly don't know how floating the patch works in a go.mod.

Maybe Tempo should have it's own build image

When/if we need to we can make our own. Otherwise we may as well share work with Loki.

[shalk]

loki-build-image 0.33.2 's golang version is 1.22.5
It works.

Let's just update to 0.33.2 if that works.

should we use golang:1.22 instead ?

I honestly don't know how floating the patch works in a go.mod.

Maybe Tempo should have it's own build image

When/if we need to we can make our own. Otherwise we may as well share work with Loki.

done

[joe-elliott]

Thanks for the fix!