luciano/babashka
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
babashka/Dockerfile

64 lines
2.3 KiB
Docker
Raw Normal View History

Improve Dockerfile, add .dockerignore (#273)
2020-02-23 20:26:45 +00:00
FROM clojure:lein-2.9.1 AS BASE
Docker
2020-02-09 21:55:12 +00:00
Build BABASHKA_STATIC with musl C library (#828) * Build BABASHKA_STATIC with musl C library Based on https://github.com/babashka/pod-babashka-aws/pull/37. This is the recommended way to build static binaries with GraalVM by the documentation and multiple issues on GitHub. See: - https://www.graalvm.org/reference-manual/native-image/StaticImages/ - oracle/graal#571 (comment) The reason that building a statically binary with glibc is complicated is explained in the glib documentation: https://sourceware.org/glibc/wiki/FAQ#Even_statically_linked_programs_need_some_shared_libraries_which_is_not_acceptable_for_me.__What_can_I_do.3F * Bring back zlib1g-dev Seems it is necessary for the non-static build.
2021-05-09 21:30:27 +00:00
ENV DEBIAN_FRONTEND=noninteractive
Improve Dockerfile, add .dockerignore (#273)
2020-02-23 20:26:45 +00:00
RUN apt update
Build BABASHKA_STATIC with musl C library (#828) * Build BABASHKA_STATIC with musl C library Based on https://github.com/babashka/pod-babashka-aws/pull/37. This is the recommended way to build static binaries with GraalVM by the documentation and multiple issues on GitHub. See: - https://www.graalvm.org/reference-manual/native-image/StaticImages/ - oracle/graal#571 (comment) The reason that building a statically binary with glibc is complicated is explained in the glib documentation: https://sourceware.org/glibc/wiki/FAQ#Even_statically_linked_programs_need_some_shared_libraries_which_is_not_acceptable_for_me.__What_can_I_do.3F * Bring back zlib1g-dev Seems it is necessary for the non-static build.
2021-05-09 21:30:27 +00:00
RUN apt install --no-install-recommends -yy curl unzip build-essential zlib1g-dev sudo
Docker
2020-02-09 21:55:12 +00:00
WORKDIR "/opt"
[#712] Upgrade to GraalVM 21.0.0 (#725)
2021-02-07 11:23:20 +00:00
RUN curl -sLO https://github.com/graalvm/graalvm-ce-builds/releases/download/vm-21.0.0/graalvm-ce-java11-linux-amd64-21.0.0.tar.gz
RUN tar -xzf graalvm-ce-java11-linux-amd64-21.0.0.tar.gz
CircleCI config
2020-04-05 21:51:26 +00:00
Build BABASHKA_STATIC with musl C library (#828) * Build BABASHKA_STATIC with musl C library Based on https://github.com/babashka/pod-babashka-aws/pull/37. This is the recommended way to build static binaries with GraalVM by the documentation and multiple issues on GitHub. See: - https://www.graalvm.org/reference-manual/native-image/StaticImages/ - oracle/graal#571 (comment) The reason that building a statically binary with glibc is complicated is explained in the glib documentation: https://sourceware.org/glibc/wiki/FAQ#Even_statically_linked_programs_need_some_shared_libraries_which_is_not_acceptable_for_me.__What_can_I_do.3F * Bring back zlib1g-dev Seems it is necessary for the non-static build.
2021-05-09 21:30:27 +00:00
ARG BABASHKA_XMX="-J-Xmx4500m"
Docs: how to build in docker + features support (#643) 1. Explain how to build `bb` for linux using docker. 2. Add support for setting the various `BABASHKA_FEATURE_*` when doing docker build via `--build-arg`.
2020-11-14 22:05:08 +00:00
[#712] Upgrade to GraalVM 21.0.0 (#725)
2021-02-07 11:23:20 +00:00
ENV GRAALVM_HOME="/opt/graalvm-ce-java11-21.0.0"
ENV JAVA_HOME="/opt/graalvm-ce-java11-21.0.0/bin"
Dockerfile
2020-05-23 13:44:17 +00:00
ENV PATH="$JAVA_HOME:$PATH"
CircleCI config
2020-04-05 21:51:26 +00:00
ENV BABASHKA_XMX=$BABASHKA_XMX
Docs: how to build in docker + features support (#643) 1. Explain how to build `bb` for linux using docker. 2. Add support for setting the various `BABASHKA_FEATURE_*` when doing docker build via `--build-arg`.
2020-11-14 22:05:08 +00:00
# Make it possible to use Docker to build bb with a particular set of features
# by setting them at build time via `docker build --build-arg ARG_NAME=true ...`
ARG BABASHKA_LEAN=
ARG BABASHKA_FEATURE_CORE_ASYNC=
ARG BABASHKA_FEATURE_CSV=
ARG BABASHKA_FEATURE_JAVA_NIO=
ARG BABASHKA_FEATURE_JAVA_TIME=
ARG BABAHSKA_FEATURE_TRANSIT=
ARG BABASHKA_FEATURE_XML=
ARG BABASHKA_FEATURE_YAML=
ARG BABASHKA_FEATURE_HTTPKIT_CLIENT=
ARG BABASHKA_FEATURE_HTTPKIT_SERVER=
ARG BABASHKA_FEATURE_JDBC=
ARG BABASHKA_FEATURE_POSTGRESQL=
ARG BABASHKA_FEATURE_HSQLDB=
ARG BABASHKA_FEATURE_ORACLEDB=
ARG BABASHKA_FEATURE_DATASCRIPT=
ARG BABASHKA_FEATURE_LANTERNA=
Build BABASHKA_STATIC with musl C library (#828) * Build BABASHKA_STATIC with musl C library Based on https://github.com/babashka/pod-babashka-aws/pull/37. This is the recommended way to build static binaries with GraalVM by the documentation and multiple issues on GitHub. See: - https://www.graalvm.org/reference-manual/native-image/StaticImages/ - oracle/graal#571 (comment) The reason that building a statically binary with glibc is complicated is explained in the glib documentation: https://sourceware.org/glibc/wiki/FAQ#Even_statically_linked_programs_need_some_shared_libraries_which_is_not_acceptable_for_me.__What_can_I_do.3F * Bring back zlib1g-dev Seems it is necessary for the non-static build.
2021-05-09 21:30:27 +00:00
ARG BABASHKA_STATIC=
Docs: how to build in docker + features support (#643) 1. Explain how to build `bb` for linux using docker. 2. Add support for setting the various `BABASHKA_FEATURE_*` when doing docker build via `--build-arg`.
2020-11-14 22:05:08 +00:00
ENV BABASHKA_LEAN=$BABASHKA_LEAN
ENV BABASHKA_FEATURE_CORE_ASYNC=$BABASHKA_FEATURE_CORE_ASYNC
ENV BABASHKA_FEATURE_CSV=$BABASHKA_FEATURE_CSV
ENV BABASHKA_FEATURE_JAVA_NIO=$BABASHKA_FEATURE_JAVA_NIO
ENV BABASHKA_FEATURE_JAVA_TIME=$BABASHKA_FEATURE_JAVA_TIME
ENV BABAHSKA_FEATURE_TRANSIT=$BABAHSKA_FEATURE_TRANSIT
ENV BABASHKA_FEATURE_XML=$BABASHKA_FEATURE_XML
ENV BABASHKA_FEATURE_YAML=$BABASHKA_FEATURE_YAML
ENV BABASHKA_FEATURE_HTTPKIT_CLIENT=$BABASHKA_FEATURE_HTTPKIT_CLIENT
ENV BABASHKA_FEATURE_HTTPKIT_SERVER=$BABASHKA_FEATURE_HTTPKIT_SERVER
ENV BABASHKA_FEATURE_JDBC=$BABASHKA_FEATURE_JDBC
ENV BABASHKA_FEATURE_POSTGRESQL=$BABASHKA_FEATURE_POSTGRESQL
ENV BABASHKA_FEATURE_HSQLDB=$BABASHKA_FEATURE_HSQLDB
ENV BABASHKA_FEATURE_ORACLEDB=$BABASHKA_FEATURE_ORACLEDB
ENV BABASHKA_FEATURE_DATASCRIPT=$BABASHKA_FEATURE_DATASCRIPT
ENV BABASHKA_FEATURE_LANTERNA=$BABASHKA_FEATURE_LANTERNA
Build BABASHKA_STATIC with musl C library (#828) * Build BABASHKA_STATIC with musl C library Based on https://github.com/babashka/pod-babashka-aws/pull/37. This is the recommended way to build static binaries with GraalVM by the documentation and multiple issues on GitHub. See: - https://www.graalvm.org/reference-manual/native-image/StaticImages/ - oracle/graal#571 (comment) The reason that building a statically binary with glibc is complicated is explained in the glib documentation: https://sourceware.org/glibc/wiki/FAQ#Even_statically_linked_programs_need_some_shared_libraries_which_is_not_acceptable_for_me.__What_can_I_do.3F * Bring back zlib1g-dev Seems it is necessary for the non-static build.
2021-05-09 21:30:27 +00:00
ENV BABASHKA_STATIC=$BABASHKA_STATIC
Docs: how to build in docker + features support (#643) 1. Explain how to build `bb` for linux using docker. 2. Add support for setting the various `BABASHKA_FEATURE_*` when doing docker build via `--build-arg`.
2020-11-14 22:05:08 +00:00
Docker
2020-02-09 21:55:12 +00:00
COPY . .
Fix docker
2020-04-28 10:12:56 +00:00
RUN ./script/uberjar
Revert
2020-02-09 22:37:01 +00:00
RUN ./script/compile
musl
2021-05-10 21:03:39 +00:00
RUN ./script/setup-musl
Docker
2020-02-09 21:55:12 +00:00
[#604] Move Docker image to Ubuntu
2020-10-01 18:06:49 +00:00
FROM ubuntu:latest
Dockerfile: Install curl to support babashka.curl (#614) With the current Ubuntu based docker image it is not possible to use babashka.curl: ``` > docker run --rm -it borkdude/babashka:0.2.3-SNAPSHOT bb '(-> "https://httpstat.us/200" babashka.curl/get :status)' ----- Error -------------------------------------------------------------------- Type: java.io.IOException Message: Cannot run program "curl": error=2, No such file or directory Location: <expr>:1:1 ----- Context ------------------------------------------------------------------ 1: (-> "https://httpstat.us/200" babashka.curl/get :status) ^--- Cannot run program "curl": error=2, No such file or directory ----- Stack trace -------------------------------------------------------------- babashka.curl/get - <built-in> user - <expr>:1:1 ``` After this change it works: ``` > docker run --rm -it hansbugge/babashka bb '(-> "https://httpstat.us/200" babashka.curl/get :status)' 200 ```
2020-10-14 15:40:52 +00:00
RUN apt-get update && apt-get install -y curl \
&& mkdir -p /usr/local/bin
Base Docker image on busybox, at least it has cat and tail
2020-02-28 17:08:05 +00:00
COPY --from=BASE /opt/bb /usr/local/bin/bb
Docker
2020-02-09 21:55:12 +00:00
CMD ["bb"]
Reference in a new issue Copy permalink