octoleo/plantuml-server
1
0
Fork 0
mirror of https://github.com/octoleo/plantuml-server.git synced 2024-12-21 16:29:03 +00:00
Code Issues Releases Wiki Activity
master
plantuml-server/Dockerfile.jetty-alpine

77 lines
2.2 KiB
Docker
Raw Permalink Normal View History

Updated Jetty and JRE in Docker, fixed Alpine build
2023-11-20 05:11:53 +00:00
FROM maven:3-eclipse-temurin-17-alpine AS builder
update docker base images and reduce size There were same base image and naming changes for the jetty and tomcat images plantuml-server uses => plantuml-server uses a pretty old and vulnerable images. - update base images for jetty and tomcat - add a alpine version for jetty (not tomcat has no official alpine version) - add autoremove and clean commands after graphviz installation. This reduces the images by about ~280 MB
2023-05-05 20:15:52 +00:00
copy `pom.parent.xml` to docker container
2023-06-09 12:59:59 +00:00
COPY pom.xml pom.parent.xml /app/
update docker base images and reduce size There were same base image and naming changes for the jetty and tomcat images plantuml-server uses => plantuml-server uses a pretty old and vulnerable images. - update base images for jetty and tomcat - add a alpine version for jetty (not tomcat has no official alpine version) - add autoremove and clean commands after graphviz installation. This reduces the images by about ~280 MB
2023-05-05 20:15:52 +00:00
COPY src/main /app/src/main/
WORKDIR /app
RUN mvn --batch-mode --define java.net.useSystemProxies=true package
########################################################################################
Updated Jetty and JRE in Docker, fixed Alpine build
2023-11-20 05:11:53 +00:00
FROM jetty:11.0.18-jre17-alpine-eclipse-temurin
update docker base images and reduce size There were same base image and naming changes for the jetty and tomcat images plantuml-server uses => plantuml-server uses a pretty old and vulnerable images. - update base images for jetty and tomcat - add a alpine version for jetty (not tomcat has no official alpine version) - add autoremove and clean commands after graphviz installation. This reduces the images by about ~280 MB
2023-05-05 20:15:52 +00:00
# Proxy and OldProxy need empty path segments support in URIs
# Hence: allow AMBIGUOUS_EMPTY_SEGMENT
# Changes are only active if `/generate-jetty-start.sh` is called!
RUN sed -i 's/# jetty\.httpConfig\.uriCompliance=DEFAULT/jetty.httpConfig.uriCompliance=DEFAULT,AMBIGUOUS_EMPTY_SEGMENT/g' /var/lib/jetty/start.d/server.ini
USER root
RUN apk add --no-cache \
curl \
font-noto-cjk \
libgd \
&& \
/generate-jetty-start.sh
#RUN apk add --no-cache graphviz
docker: use always latest Graphviz release This will change the Graphviz behaviour inside the docker container. Until now it was always a fixed Graphviz version inside the Dockerfile. With these changes the docker container will always use the latest Graphviz release if the version was not manually set via the docker build argument `GRAPHVIZ_VERSION`. If not set as build arg fetch latest version of Graphviz based on their release name by default. An alternative would be to use `tag_name`. Also, to avoid the overhead of getting all kinds of relase data, GitLabs GraphQL interface could be used. ```bash curl -s \ -H "Content-Type:application/json" \ -d '{"query": "{project(fullPath:\"graphviz/graphviz\"){releases(first:5,sort:RELEASED_AT_DESC){nodes{name}}}}"}' \ "https://gitlab.com/api/graphql" \ | jq -r '.data.project.releases.nodes[].name' | sort -V -r | head -n 1 ``` In GraphQL the alternative to `name` would be `tagName`.
2023-05-05 15:38:28 +00:00
ARG GRAPHVIZ_VERSION
update docker base images and reduce size There were same base image and naming changes for the jetty and tomcat images plantuml-server uses => plantuml-server uses a pretty old and vulnerable images. - update base images for jetty and tomcat - add a alpine version for jetty (not tomcat has no official alpine version) - add autoremove and clean commands after graphviz installation. This reduces the images by about ~280 MB
2023-05-05 20:15:52 +00:00
ARG GRAPHVIZ_BUILD_DIR=/tmp/graphiz-build
RUN apk add --no-cache \
g++ \
docker: use always latest Graphviz release This will change the Graphviz behaviour inside the docker container. Until now it was always a fixed Graphviz version inside the Dockerfile. With these changes the docker container will always use the latest Graphviz release if the version was not manually set via the docker build argument `GRAPHVIZ_VERSION`. If not set as build arg fetch latest version of Graphviz based on their release name by default. An alternative would be to use `tag_name`. Also, to avoid the overhead of getting all kinds of relase data, GitLabs GraphQL interface could be used. ```bash curl -s \ -H "Content-Type:application/json" \ -d '{"query": "{project(fullPath:\"graphviz/graphviz\"){releases(first:5,sort:RELEASED_AT_DESC){nodes{name}}}}"}' \ "https://gitlab.com/api/graphql" \ | jq -r '.data.project.releases.nodes[].name' | sort -V -r | head -n 1 ``` In GraphQL the alternative to `name` would be `tagName`.
2023-05-05 15:38:28 +00:00
jq \
Updated Jetty and JRE in Docker, fixed Alpine build
2023-11-20 05:11:53 +00:00
expat-dev \
update docker base images and reduce size There were same base image and naming changes for the jetty and tomcat images plantuml-server uses => plantuml-server uses a pretty old and vulnerable images. - update base images for jetty and tomcat - add a alpine version for jetty (not tomcat has no official alpine version) - add autoremove and clean commands after graphviz installation. This reduces the images by about ~280 MB
2023-05-05 20:15:52 +00:00
make \
zlib \
Updated Jetty and JRE in Docker, fixed Alpine build
2023-11-20 05:11:53 +00:00
pkgconf \
update docker base images and reduce size There were same base image and naming changes for the jetty and tomcat images plantuml-server uses => plantuml-server uses a pretty old and vulnerable images. - update base images for jetty and tomcat - add a alpine version for jetty (not tomcat has no official alpine version) - add autoremove and clean commands after graphviz installation. This reduces the images by about ~280 MB
2023-05-05 20:15:52 +00:00
&& \
mkdir -p $GRAPHVIZ_BUILD_DIR && \
cd $GRAPHVIZ_BUILD_DIR && \
docker: use always latest Graphviz release This will change the Graphviz behaviour inside the docker container. Until now it was always a fixed Graphviz version inside the Dockerfile. With these changes the docker container will always use the latest Graphviz release if the version was not manually set via the docker build argument `GRAPHVIZ_VERSION`. If not set as build arg fetch latest version of Graphviz based on their release name by default. An alternative would be to use `tag_name`. Also, to avoid the overhead of getting all kinds of relase data, GitLabs GraphQL interface could be used. ```bash curl -s \ -H "Content-Type:application/json" \ -d '{"query": "{project(fullPath:\"graphviz/graphviz\"){releases(first:5,sort:RELEASED_AT_DESC){nodes{name}}}}"}' \ "https://gitlab.com/api/graphql" \ | jq -r '.data.project.releases.nodes[].name' | sort -V -r | head -n 1 ``` In GraphQL the alternative to `name` would be `tagName`.
2023-05-05 15:38:28 +00:00
GRAPHVIZ_VERSION=${GRAPHVIZ_VERSION:-$(curl -s https://gitlab.com/api/v4/projects/4207231/releases/ | jq -r '.[] | .name' | sort -V -r | head -1)} && \
update docker base images and reduce size There were same base image and naming changes for the jetty and tomcat images plantuml-server uses => plantuml-server uses a pretty old and vulnerable images. - update base images for jetty and tomcat - add a alpine version for jetty (not tomcat has no official alpine version) - add autoremove and clean commands after graphviz installation. This reduces the images by about ~280 MB
2023-05-05 20:15:52 +00:00
curl -o graphviz.tar.gz https://gitlab.com/api/v4/projects/4207231/packages/generic/graphviz-releases/${GRAPHVIZ_VERSION}/graphviz-${GRAPHVIZ_VERSION}.tar.gz && \
tar -xzf graphviz.tar.gz && \
cd graphviz-$GRAPHVIZ_VERSION && \
./configure && \
make && \
make install && \
apk del --no-cache \
g++ \
docker: use always latest Graphviz release This will change the Graphviz behaviour inside the docker container. Until now it was always a fixed Graphviz version inside the Dockerfile. With these changes the docker container will always use the latest Graphviz release if the version was not manually set via the docker build argument `GRAPHVIZ_VERSION`. If not set as build arg fetch latest version of Graphviz based on their release name by default. An alternative would be to use `tag_name`. Also, to avoid the overhead of getting all kinds of relase data, GitLabs GraphQL interface could be used. ```bash curl -s \ -H "Content-Type:application/json" \ -d '{"query": "{project(fullPath:\"graphviz/graphviz\"){releases(first:5,sort:RELEASED_AT_DESC){nodes{name}}}}"}' \ "https://gitlab.com/api/graphql" \ | jq -r '.data.project.releases.nodes[].name' | sort -V -r | head -n 1 ``` In GraphQL the alternative to `name` would be `tagName`.
2023-05-05 15:38:28 +00:00
jq \
Updated Jetty and JRE in Docker, fixed Alpine build
2023-11-20 05:11:53 +00:00
expat-dev \
update docker base images and reduce size There were same base image and naming changes for the jetty and tomcat images plantuml-server uses => plantuml-server uses a pretty old and vulnerable images. - update base images for jetty and tomcat - add a alpine version for jetty (not tomcat has no official alpine version) - add autoremove and clean commands after graphviz installation. This reduces the images by about ~280 MB
2023-05-05 20:15:52 +00:00
make \
zlib \
&& \
rm -rf $GRAPHVIZ_BUILD_DIR
COPY docker-entrypoint.jetty.sh /entrypoint.sh
RUN chmod +x /entrypoint.sh
USER jetty
ENV WEBAPP_PATH=$JETTY_BASE/webapps
RUN rm -rf $WEBAPP_PATH && \
mkdir -p $WEBAPP_PATH
COPY --from=builder /app/target/plantuml.war /plantuml.war
COPY ROOT.jetty.xml $WEBAPP_PATH/ROOT.xml
# Openshift https://docs.openshift.com/container-platform/4.9/openshift_images/create-images.html#images-create-guide-openshift_create-images
USER root
RUN chgrp -R 0 $JETTY_BASE && \
chmod -R g=u $JETTY_BASE
RUN chgrp -R 0 /tmp && \
chmod -R g=u /tmp
USER jetty
ENTRYPOINT ["/entrypoint.sh"]
VOLUME ["/tmp/jetty"]
Copy Permalink