Script Language Containers 10.0.0 available on GitHub: leaner template build flow, dependency updates, internal improvements

General
,
1

Summary
We’ve published script-languages-release 10.0.0 on GitHub: https://github.com/exasol/script-languages-release. This release introduces a streamlined build process for template flavors to reduce the size of intermediate Docker images, plus dependency updates and internal improvements.

Important note: This is a GitHub-only release only. Future versions may be considered for pre-installation of Script Language Containers (SLCs) in Exasol database.

What changed

  • Template flavor build process: Adjusted to produce smaller intermediate Docker layers, improving build efficiency and reducing local/registry storage usage.

  • Dependency updates: Refreshed third-party packages to current, supported versions for stability and security.

  • Internal improvements: General maintenance and cleanup to improve reliability and developer experience.

Why it matters

  • Faster CI/CD: Smaller layers usually result in quicker pushes/pulls and better cache behavior.

  • Lower storage footprint: Keeps local caches and registries leaner.

  • Up-to-date dependencies: Reduces vulnerability exposure and incorporates upstream fixes.

Who should act

  • Teams building custom Script Language Containers or extending templates in their own pipelines.

  • Maintainers who mirror or curate container images in internal registries.

Actions

  • If you rely on GitHub builds, update your references to 10.0.0 and rebuild to benefit from the leaner intermediate layers.

  • Review any custom template flavor overrides or extensions to ensure compatibility with the adjusted build flow.

  • No action is required for users who rely solely on the preinstalled SLCs in the database.

Validation checklist

  • Confirm CI runners build without changes to required build arguments or environment variables.

  • Compare image sizes before/after in your environment.

  • Smoke-test UDFs/scripts that depend on these images.

Docs and housekeeping

  • Add a short note in internal docs if you maintain instructions for customizing or extending SLC templates.

  • Consider registry cleanup policies to retire older, larger intermediates where safe.

Support If you encounter build regressions or dependency conflicts, please share:

  • Template flavor and relevant Dockerfile snippet

  • CI logs (buildx/buildkit versions, cache settings)

  • Runner details (Docker/Podman versions)

  • We’re happy to help triage and provide migration guidance.

1 Like