Skip to content

Conversation

@MoeMahhouk
Copy link
Member

@MoeMahhouk MoeMahhouk commented Jan 27, 2025

This PR does the following:

  • adds Dockerfile to build a reproducible distroless image of the reverse proxy (server & client)
  • adds github release workflow that runs two docker builds in parallel for both server and client and pushes the results to ghcr
  • adds build flags for reproducible builds.

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

@MoeMahhouk MoeMahhouk marked this pull request as ready for review January 27, 2025 17:45
Copy link
Contributor

@metachris metachris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

awesome, thanks

@MoeMahhouk MoeMahhouk merged commit 0b7e36e into main Jan 28, 2025
2 checks passed
@MoeMahhouk MoeMahhouk deleted the reproducible-builds branch January 28, 2025 14:22
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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants