Fix Docker image runs erroring due to glibc incompatability #572
Conversation
This file contains 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
hi019
changed the title
|
Last time I used a recent Debian, we had a terrible regression in network performance. I would look out for those as you deploy your Docker images to production, but this is much better than not being able to start it at all. Thank you! |
|
Thanks for the heads up, will keep this in mind :) |
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.
The base Docker image used for building, rust:1, is running a different version of glibc than that of the image used for executing pgcat, debian:bullseye. And apparently Rust requires the that the glibc version used for building be compatible with the one used to execute the binary (rust-lang/rust#57497).
This PR fixes that and also upgrades the Debian version.