We spent some time investigating this with @eskombro yesterday, and could not come up with a reasonable solution. The trick would be to copy the .git folder over in the wordir used by docker to build the binary, as vergen, the dependency we use to retrieve this info, looks at .git/HEAD. A nicer solution IMO would be for the production container to use github release binary instead of the one built in the current recipe

Yes, the problem is due to the .git folder not being accessible by the vergen dependency.
As you said we can either copy the .git/HEAD file to the docker build container.

Using the github release binary inside of the docker container will probably be harder to do because both, the docker and the binaries are currently built at the same time, and therefore the docker image will not be able to access the binaries. I think with Github Action we could specify that a certain build must run after another one, we should look into that.

If we do so we will have to create two GA pipelines, one for the common PRs and one for the releases.

If we do so we will have to create two GA pipelines, one for the common PRs and one for the releases.

that seems like a reasonable solution

Also build time for the container is up to 15min (we checked yesterday with @eskombro), it may not be desirable when you only want to run the container right away