mirror of
https://github.com/yrutschle/sslh.git
synced 2025-04-12 23:27:15 +03:00
db5ed29fa2
As per docker guidelines [0] a container should always really have a consistent entrypoint, without having to override it or do special tricks. The behavior should be _identical_ as before, but will no longer trigger errors because sslh doesn't understand certain parameters (/bin/sh for example being common). Further more, allows a proper entrypoint for a CI to work easily with the container as well. Allowing for scenario's such as `apk add git && sslh --foreground` in your sslh image for example. E.g. `docker run sslh --help` works though with the default `--foreground` a bit weirdly, as does `docker run sslh /bin/sh` or `docker run sslh ls`. [0]: https://github.com/docker-library/official-images#consistency Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
25 lines
391 B
Docker
25 lines
391 B
Docker
FROM alpine:latest as build
|
|
|
|
WORKDIR /sslh
|
|
|
|
COPY . /sslh
|
|
RUN \
|
|
apk add \
|
|
gcc \
|
|
libconfig-dev \
|
|
make \
|
|
musl-dev \
|
|
pcre2-dev \
|
|
perl && \
|
|
make sslh-select && \
|
|
strip sslh-select
|
|
|
|
FROM alpine:latest
|
|
|
|
COPY --from=build "/sslh/sslh-select" "/usr/local/bin/sslh"
|
|
|
|
RUN apk --no-cache add libconfig pcre2
|
|
|
|
COPY "./container-entrypoint.sh" "/init"
|
|
ENTRYPOINT [ "/init" ]
|