chore: Add reproducible build docker and github release workflow #28
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3 tasks
MoeMahhouk
added a commit
to flashbots/buildernet-orderflow-proxy
that referenced
this pull request
Feb 4, 2025
## 📝 Summary This PR adjusts the receiver.dockerfile to support reproducible builds. It also adds a CI pipeline action to build a reproducible container image using kaniko for the receiver proxy ## ⛱ Motivation and Context For the future BuilderNet with containerization of services, we need to containerize the receiver proxy to use it within the image. ## 📚 References [This is similar to the work in this PR](flashbots/cvm-reverse-proxy#28) --- ## ✅ I have run these commands * [ ] `make lint` * [ ] `make test` * [ ] `go mod tidy`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR does the following:
Current open issue:
when rebuilding the docker image from scratch after clearing cache, it is not reproducing the same docker image hash/digest again. More investigations are necessary as not only the reproducible binary is necessary here but also the final image hash too.
Update: This is no longer an issue because now we adjusted the CI to use kaniko to build the image reproducibly