Hi all,
unsetting the parent image's entrypoint is rather a workaround than a solution.
The issue is that the Maven image tries to copy some configuration into the
Maven configuration directory (seems to be required for users still relying on
Maven during container runtime, we're only using Mav
Hi BaseX-Talk,
in case any of you is using our docker images, in recent builds there seems to
be a bug related to the ENTRYPOINT and the PARENT mvn Image we are using.
If you encounter the following error message (in fact you should if you docker
pulled recently ;-)):
> ⇒ docker run basex/ba
2 matches
Mail list logo
