-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(container image): fix ssl3 runtime dep, update to debian 12 bookworm, upgrade rust #116
Conversation
Sinker got ssl security updates that requires libssl.so.3 which debian bullseye doesn't have. Update to bookworm image.
no it appears bookworm-slim doesn't have libssl.so.3 either. |
Updates the sinker dockerfile following what iox does for a runtime image with libssl3 libraries, also create sinker user and group on the container.
This pr is ready to review. |
docker buildx imagetools inspect <image> will show the overall manifest sha unlike docker hub which only shows shas for specific platforms.
I tested an image from this docker file in local dev - it runs. by editing |
In bisecting an issue with the sinker readiness and liveness probes, i discovered it wasn't the ssl dep upgrade that need libssl3 but the rust toolchain upgrade in #83 see comment https://github.com/influxdata/k8s-idpe/pull/35968#issuecomment-1876291232 |
Sinker got ssl security updates that requires libssl.so.3 which debian bullseye doesn't have. So sinker pods can't run. To resolve, i upgraded to bookworm images, upgraded rust to 1.74, copied over what the iox dockerfile does to bring in the libssl3 libraries, added a sinker user (also following iox's dockerfile).
apt install libssl3
was the critical piece.The new runtime container image is 122MB. The previous image is 94MB.
pod error
I believe this works although proving it on my M2 Max is difficult.