Dockerfile

# syntax = docker/dockerfile:1.2

FROM --platform=$TARGETPLATFORM registry.access.redhat.com/ubi8/ubi:latest

RUN \
  yum install -y \
    gcc \
    git \
    glibc-langpack-en \
    java-11-openjdk-devel \
    jq \
    make \
    patch \
    which \
  && yum clean all

# Ensure Logstash gets a UTF-8 locale by default.
ENV LANG='en_US.utf8' LC_ALL='en_US.utf8'

RUN groupadd --gid 1000 builder && \
    adduser --uid 1000 --gid 1000 \
      --home-dir /src --create-home \
      builder

RUN  install -d -o builder -g builder -m 0775 /src \
  && install -d -o builder -g builder -m 0775 /opt/jruby

# Note: While the official logstash Docker container runs logstash in Java 11,
# the plugin eco-system is still built with Java 8, because Java 8 is still
# supported. Indeed, you'll find a number of issues (mostly relating to
# gradle wrapper and build.gradle files) that will require updating to work
# with Java 11

USER builder
WORKDIR /src

ENV LS_HOME=/src/logstash

# Build logstash for the Open Source version; shouldn't
# affect plugins.
#
ENV OSS=true

# This was in the master branch, but not the 7.9 branch...
ENV LOGSTASH_SOURCE=1
ENV LOGSTASH_PATH=${LS_HOME}

# Get logstash and assemble its Java bits
# We do this before installing JRuby, because
# the Logstash source tells us which version
# of JRuby it wants.

RUN git clone --branch 7.17 --single-branch https://github.com/elastic/logstash.git

# I had originally wanted this to be a --mount=type=cache, but gradlew complained that
# it couldn't create an exclusive lock within there...
#
RUN --mount=type=cache,target=/src/.gradle,uid=1000,gid=1000 \
  set -eu; \
  cd ${LS_HOME}; \
  ./gradlew assemble

# For Ruby stuff, we want a copy of jruby that matches what Logstash uses for
# whichever version we're building.
#
# We could use tools like RVM, but that will end up building Ruby/Jruby from
# source, with lots of dependencies; so we just download the binary tar.gz
# package made from jruby.org, and be sure to check compare the checksum
# to what is expected for that version.
#
# https://www.jruby.org/download

# If using Java 11, then you need to have JRuby 9.2, otherwise
# you'll end up with version detection error when starting jruby
# and it will try to load some things (eg. ScriptEngine) for
# Java 7, which will not work.

# See version.yml in the logstash repo
#
ARG jruby_version=9.2.20.1

# See versions.yml in the logstash repo
#
COPY CHECKSUMS-jruby /tmp

RUN --mount=type=cache,target=/cache/,uid=1000,gid=1000 \
  set -xeu; \
  tarball="/cache/jruby-dist-${jruby_version}-bin.tar.gz"; \
  ls -ld /cache ; \
  curl -s -o "${tarball}" \
      https://repo1.maven.org/maven2/org/jruby/jruby-dist/${jruby_version}/jruby-dist-${jruby_version}-bin.tar.gz; \
  cd /cache; \
  sha1sum --ignore-missing --check /tmp/CHECKSUMS-jruby; \
  mkdir -p /opt/jruby; \
  tar -C /opt/jruby -zxf /cache/jruby-dist-${jruby_version}-bin.tar.gz --strip-components=1 --no-same-owner

# NOTE: I've found (same as https://github.com/elastic/logstash-devutils/issues/68)
# that if logstash/bin is in the PATH before jruby/bin, then you'll get problems
# resolving dependencies (notably logstash-devutils). But if jruby/bin is in the
# PATH before logstash/bin, then it works.
#
#ENV PATH=/src/logstash/bin/:/opt/jruby/bin:${PATH}
# Actually, that might be wrong; had issues with belzebuth dependencies (and then
# more)
ENV PATH=/opt/jruby/bin:/src/logstash/bin:/src/bin:${PATH}

RUN jruby --version

RUN --mount=type=cache,target=/src/.gradle,uid=1000,gid=1000 \
  gem install bundler -v 2.3.27 && gem install rake

# Now that we have 'rake' available, we need to bootstrap the logstash source
# to provide ... jruby (a vendored version of it) and more besides.

RUN set -eu; cd ${LS_HOME}; cp Gemfile.jruby-2.5.lock.release Gemfile.lock

RUN --mount=type=cache,target=/src/.gradle,uid=1000,gid=1000 \
  set -eu; cd ${LS_HOME}; rake bootstrap

# It would be useful to have the usual plugins available, as
# they are not installed by default; they take ages to install too,
# for some reason.

RUN --mount=type=cache,target=/src/.gradle,uid=1000,gid=1000 \
  cd ${LS_HOME}; rake plugin:install-default

# When we compile a new plugin, we invoke 'bundle install' and it will go away
# and pull down yet more stuff from the internet; which sucks if you're offline.
# So let's generate a simple filter plugin with the minimal bits it needs,
# compile it and test it to ensure that it works.

RUN logstash-plugin generate --type=filter --name=buildtest --path=/src/
COPY logstash-filter-buildtest/logstash-filter-buildtest.gemspec \
    /src/logstash-filter-buildtest/logstash-filter-buildtest.gemspec
COPY logstash-filter-buildtest/Gemfile \
    /src/logstash-filter-buildtest/Gemfile
RUN cd /src/logstash-filter-buildtest && bundle install
RUN cd /src/logstash-filter-buildtest && bundle exec rspec

# TODO: Should build a Java plugin too...

# Support the use of 'Drip' to make dealing with long startup times more pleasant.
# This will really help with running tests quickly and often.
# Drip works by keeping another JVM ready in the background, with the same classpath
# and startup options, ready to go. It's been around for years now, and the master
# branch was last updated a few years ago, which is rather newer than the last release.
#
# Keep an occassional eye on https://github.com/ninjudd/drip/network to see if this
# moves to somewhere else.
#
# You'll need to set JAVACMD=`which drip` for this to be used... I don't see much
# difference (if any) though, so not sure if that's working as it should.
# Also, the checksum is not so useful; it downloads other things too.
#
RUN mkdir -p ~/bin/ && \
    rm -f ~/bin/drip && \
    curl -sL https://raw.githubusercontent.com/ninjudd/drip/master/bin/drip > ~/bin/drip && \
    sha256sum ~/bin/drip | tee /dev/stderr | grep -q acffc2af7385af993949d2fc406c456d1edf1a542fb72d2f2c7758251226c89c && \
    chmod +x ~/bin/drip && \
    echo "Drip downloaded and matches expected checksum"

WORKDIR /work

ENTRYPOINT ["/bin/bash"]