[K8s] Fix default runtime build broken by Debian Buster EOL#1460
Merged
JosepSampe merged 1 commit intolithops-cloud:masterfrom May 5, 2026
Merged
Conversation
Member
|
Thanks for the contribution @mskuratowski ! |
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
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.
Problem
The default k8s runtime build (
lithops/serverless/backends/k8s/k8s.py:175andruntime/kubernetes/Dockerfile) bases onpython:*-slim-buster. Debian 10 (Buster) reached EOL in June 2024 and its APT repos moved to archive, so the generatedRUN apt-get updatefails with 404s and the build aborts. Every new k8s user following the documented "default runtime is built the first time you execute a function" flow hits this.Fix
slim-bookwormtag published), add 3.11 / 3.12.Dockefile.default-k8s-runtime→Dockerfile.default-k8s-runtime.Developer's Certificate of Origin 1.1