fix: glibc runtime errors

[dylanlott]

fix: glibc runtime errors

This PR updates the docker stage 0 to use a known version of bookworm​ in for the next cargo-chef​ build step instead of the lukemathwalker/cargo-check​ image that it previously used in order to maintain glibc​ compatibility with the debian:bookwork-slim​ image used in stage 3.

Testing

Built a container with github actions and ran it in DevNet - tl;dr it landed blocks and the runtime error was gone.

Closes ENG-1424

[dylanlott]

• wip: adds a flashbots provider #158
• fix: glibc runtime errors #159 👈 (View in Graphite)
• update alloy and add provider-mev-api flag #157
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Evalir]

this locks our rust version used in the dockerfile and this is something i'd preferably not want to track. Can't we use a "latest stable" image?

[rswanson]

I concur, specifically I think we'd want the tag slim as that appears to be the equivalent of latest slim and I can't think of a good reason to pin to the version of debian at all. I think slim has everything we need (with the installs)

[rswanson]

What changed that impacted glibc btw, just curious

[dylanlott]

Root cause was that 5 days ago, a new release of cargo-chef's changed the version of glibc in the lukemathwalker/cargo-chef builds to a newer version of glibc than was compatible with the builder runtime stage 3, so builds on main branch were building but erroring at runtime. Changing to the rust:bookworm image aligns the glibc version with what's available in stage 3's bookworm-slim image.

Re: Image version - Version specification can loosen to rust:1-bookworm or even rust:bookworm. Those are much less strict and still solve the glibc issue and prevent it popping up in the future. I've updated it to rust:bookworm for now.

[rswanson]

this works

[Evalir]

perfect

[dylanlott]

Merge activity

• Oct 8, 9:16 AM UTC: @dylanlott merged this pull request with Graphite.