Skip to content
This repository has been archived by the owner on Jun 15, 2019. It is now read-only.

Build netty-tcnative native binaries for Alpine Linux.

License

Notifications You must be signed in to change notification settings

pires/netty-tcnative-alpine

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

15 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

netty-tcnative-alpine

Docker container used to build netty-tcnative binaries for Alpine Linux.

ARCHIVED

According to @ejona86

This is just FYI, but I did some recent testing on Alpine and I discovered that netty-tcnative-boringssl-static works without issue on standard Alpine.

For openjdk:8-jre-alpine, I ran apk update && apk add libc6-compat while generating the docker image.

For alpine:latest, I ran apk update && apk add openjdk8-jre-base libc6-compat.

adoptopenjdk/openjdk8:alpine-slim and adoptopenjdk/openjdk11:alpine-slim worked out-of-the-box.

Pre-requisites

  • Docker

Bootstrap builder

$ docker build --build-arg NETTY_TCNATIVE_TAG=netty-tcnative-parent-2.0.7.Final -t pires/netty-tcnative-alpine:2.0.7.Final .

Build binaries

$ mkdir binaries
$ docker run -v `pwd`/binaries:/output pires/netty-tcnative-alpine:2.0.7.Final

Binaries should become available in binaries folder:

$ ls -lh binaries

Use binaries

One needs an alpine container, obviouslly and libuuid dependency, otherwise even boringssl-static won't work.

FROM alpine:3.7

RUN apk add --update libuuid

Acknowledgements

  • Work inspired by @dimitarg stuff
  • Kudos to @ejona86 for helping with this!