[
https://issues.apache.org/jira/browse/IMPALA-13825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laszlo Gaal resolved IMPALA-13825.
----------------------------------
Fix Version/s: Impala 5.0.0
Resolution: Fixed
> Impala Docker images should be able to use custom base images
> -------------------------------------------------------------
>
> Key: IMPALA-13825
> URL: https://issues.apache.org/jira/browse/IMPALA-13825
> Project: IMPALA
> Issue Type: New Feature
> Components: Infrastructure
> Reporter: Laszlo Gaal
> Assignee: Laszlo Gaal
> Priority: Major
> Labels: build, docker
> Fix For: Impala 5.0.0
>
>
> Impala already supports running all daemons inside Docker containers, so it
> can be deployed in Kubernetes clusters; some downstream versions are actually
> released this way as products.
> Packaging Impala into this form factor is also supported, but the base
> container images are currently chosed implicitly by the build process, based
> on the native OS platform of the build system. This is done to ensure that
> the Impala binaries produced by the build running natively on the build
> platform can be installed into the Docker containers with no compatibility
> problems as far as library version dependencies are concerned.
> Modern security practices in cloud-based environments started requiring
> special, locked-down and slimmed-down base images for containerized
> workloads, e.g. distroless images, Ubuntu Chiselled images, or Chainguard's
> Wolfi OS. These all share the common requirement that the Impala binaries
> need to be installable into a specific, prescribed base image, possibly given
> to the build process by some external actor, so Impala's Docker build logic
> should be extended to be able to accept and accommodate such explicitly
> specified external base images.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
