You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As noted by @marioevz in ChainSafe/lodestar#6276 (Additional context) it looks like the Lodestar image unstable-linux-amd64 does not include the commit hash in version info. This makes it difficult to determine the exact version (code) that is running based on the logs.
Based on the workflows of this repo it looks like it uses the Dockerfile from the Lodestar repo to build the image but does not pass the COMMIT build arg which is required to write git data.
For reference, this is how we pass the commit hash in our build step
--build-arg COMMIT=$(git rev-parse HEAD)
The text was updated successfully, but these errors were encountered:
As noted by @marioevz in ChainSafe/lodestar#6276 (Additional context) it looks like the Lodestar image unstable-linux-amd64 does not include the commit hash in version info. This makes it difficult to determine the exact version (code) that is running based on the logs.
Based on the workflows of this repo it looks like it uses the Dockerfile from the Lodestar repo to build the image but does not pass the
COMMIT
build arg which is required to write git data.For reference, this is how we pass the commit hash in our build step
--build-arg COMMIT=$(git rev-parse HEAD)
The text was updated successfully, but these errors were encountered: