acceptable-knife-37130
12/10/2025, 3:57 AMImage.from_base and Image.from_debian_base . It appears to have the same functionality. There are a few extra parameters for debian base as below:
python_version: Tuple[int, int] | None = None,
flyte_version: str | None = None,
install_flyte: bool = True,
registry: str | None = None,
registry_secret: str | Secret | None = None,
name: str | None = None,
platform: Tuple[Architecture, ...] | None = None
Why weren’t those added to the Image.from_base function. I presume Image.from_base can also be an debian image.
Can someone look at the example file : flyte-sdk/examples/image/base_image.py , the image defined is never used.
image = (
Image.from_debian_base(install_flyte=False)
.with_apt_packages("vim", "wget")
.with_pip_packages("mypy", pre=True)
.with_env_vars({"hello": "world1"})
.with_dockerignore(Path(__file__).parent / ".dockerignore")
.with_local_v2()
)
env = flyte.TaskEnvironment(name="t1", image=Image.from_base(image_uri="docker.io/library/debian:latest"))
If you support for ``Image.from_debian_base`` would there be function to provide support for other distributions like RPM etc.echoing-account-76888
12/10/2025, 5:38 AMechoing-account-76888
12/10/2025, 5:39 AMacceptable-knife-37130
12/10/2025, 5:42 AMImage.from_base and then people can define the image URL etc.
Also Image.from_base will require those extra parameters as in Image.from_debian_base . I might be wrong but i see Image.from_debian_base as unnecessary.echoing-account-76888
12/10/2025, 6:57 AMfrom_debian_base and it's clear that we are using the debian as base image.
For using from_base , the extra parameter can be set through .clone (example)
cc @glamorous-carpet-83516 @freezing-airport-6809 @thankful-minister-83577 to check the design choice here