docklands Wildfly image

I'm new to docker and just started to experiment with docker. Therefor I used the docklands wildfly image. Starting wildfly with an ENTRYPOINT causes the image to not react on image shutdownhook and the wildfly ist just killed.

From the docker reference:

The shell form prevents any CMD or run command line arguments from being used, but has the disadvantage that your ENTRYPOINT will be started as a subcommand of /bin/sh -c, which does not pass signals. This means that the executable will not be the container’s PID 1 - and will not receive Unix signals - so your executable will not receive a SIGTERM from docker stop .

Jan 18 '17 10:01 devylon

Do you need to gracefully download wildfly? Just killing it is faster :-)

Sep 29 '17 09:09 AdamBien

I'm running camel within wildfly. And some of the camel routes need a graceful shutdown.

Sep 29 '17 10:09 devylon

I really like Adam. He does a great job. But at least for docklands/wildfly I prefer to use the official jboss/wildfly for several reasons:

It's always up-to-date (currently 16.0.0 over 15.0.0).
It uses a stable path /opt/jboss/wildfly/ so I can add deployments without repeating the version number.
It uses a system user (created with -r), which is more secure.
It registers shutdown hooks. And probably there are many more reasons that I just didn't see, yet.

Mar 08 '19 08:03 t1

okay, Adam just release an update to 16.0.0, so my first point is obsolete (for now) ;-)

Mar 14 '19 07:03 t1