dongjoon-hyun opened a new pull request, #574: URL: https://github.com/apache/spark-connect-swift/pull/574
### What changes were proposed in this pull request? This PR aims to upgrade the base image of the Swift examples (`app`, `pi`, `spark-sql`, `stream`) from `gcr.io/distroless/static-debian12:nonroot` to `gcr.io/distroless/static-debian13:nonroot`. ### Why are the changes needed? To use the latest Debian 13 (Trixie)-based distroless image. Since the example binaries are fully statically linked via the Swift Static Linux SDK (`*-swift-linux-musl`), they don't depend on the base image's libc. The two images have the same runtime configuration: | | `static-debian12:nonroot` | `static-debian13:nonroot` | |---|---|---| | `linux/amd64`, `linux/arm64` | Yes | Yes | | User | `65532` | `65532` | | WorkingDir | `/home/nonroot` | `/home/nonroot` | | `SSL_CERT_FILE` | `/etc/ssl/certs/ca-certificates.crt` | `/etc/ssl/certs/ca-certificates.crt` | ### Does this PR introduce _any_ user-facing change? No behavior change. Only the base image of the example Docker images is changed. ### How was this patch tested? Manually built all four example images and ran the `pi` example against an Apache Spark 4.2.0 Spark Connect server. ``` $ docker build -t spark-connect-swift:pi Examples/pi $ docker network create sc $ docker run -d --rm --name spark --network sc -e SPARK_NO_DAEMONIZE=1 apache/spark:4.2.0 bash -c /opt/spark/sbin/start-connect-server.sh $ docker run --rm --network sc -e SPARK_REMOTE=sc://spark:15002 spark-connect-swift:pi Pi is roughly 3.142036 ``` The image size increases by about 141KB (`linux/arm64`, Docker 29.5.3). The `docker images` example outputs in `Examples/*/README.md` (`112MB` / `32MB`) remain valid. | Image | Base | DISK USAGE | CONTENT SIZE | Size (bytes) | |---|---|---|---|---| | `pi` | `static-debian12:nonroot` | 112MB | 32.1MB | 32,049,596 | | `pi` | `static-debian13:nonroot` | 112MB | 32.2MB | 32,190,818 | | `app`, `spark-sql`, `stream` | `static-debian13:nonroot` | 112MB | 32.2MB | - | ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Opus 5.5 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
