Hi,
sadly, Tanuki Wrapper license has changed a while ago, and in order to
keep the version compatible with what we require at the ASF, we are
stuck with version 3.2.3. They moved to GPL - an incompatible license -
in 3.3.0.
The wrapper version 3.2.3 is ... 17 years old!
I do think we should go with yajsw [1] which offer some kind of
compatibility and which license is ASF compatible.
[1] https://yajsw.sourceforge.io/
On 29/09/2023 19:20, T. Schapitz wrote:
Hi there,
just a heads up: I'm currently tinkering to set up a minimalist docker
image for ApacheDs.
I know, there are already some out there, but to understand things, I
tried my hand. Since my base image was the alpine:latest stacked with
JDK 20 on top, I used the .bin installer (there are no Alpine apk
packages for ApacheDs) with default settings, resulting the server and
the default instance all in the right places. After having sorted out
various other problems, the Tanuki wrapper is giving me headaches:
What ever I try starting the server, I'm getting:
----------------
Starting ApacheDS - default...
/opt/apacheds-2.0.0.AM26/bin/apacheds: eval: line 402:
/opt/apacheds-2.0.0.AM26/bin/wrapper: not found
------------------
This is funny, because an ls results in:
------------------
/ $ ls -al /opt/apacheds-2.0.0.AM26/bin/wrapper
-rwxr-xr-x 1 apacheds apacheds 111027 Sep 27 20:41
/opt/apacheds-2.0.0.AM26/bin/wrapper
------------------
Trying to invoke the wrapper directly from the command line:
------------------
/ $ /opt/apacheds-2.0.0.AM26/bin/wrapper
sh: /opt/apacheds-2.0.0.AM26/bin/wrapper: not found
------------------
which leads me to believe, there might be something wrong with the wrapper.
I consulted Tanuki's site, but they state, that the wrapper is meant to
work with JDK 20 - which might be missleading, because JDK 20 was
released 21 April 2023 - well after 2.0.0.AM26 has been packaged, so the
copy therein might not yet be ready for JDK 20.
I also tried to get some more verbosity by using wrapper.debug=TRUE, but
this didn't help either.
Do I miss something there? Has anybody else seen something similar? Are
there known limitations regarding the JDK?
If seen in he issues, that someone suggested to replace it with Apaches
own brand of wrapper.
Greetings,
Thomas
P. S. I'm probably going to skip the wrapper entirely, as I see no point
in having functionality, that is covered by kubernetes duplicated by it
within the container.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@directory.apache.org
For additional commands, e-mail: users-h...@directory.apache.org
--
*Emmanuel Lécharny* P. +33 (0)6 08 33 32 61
elecha...@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@directory.apache.org
For additional commands, e-mail: users-h...@directory.apache.org
