Hi George,

Hi, I just wanted to let you know that pulling previous docker images (for example 8.4.4) after the latest changes, made them unable to run.

The error is:

...

touch: cannot touch ‘/root/.m2/copy_reference_file.log’: Permission denied Can not write to /root/.m2/copy_reference_file.log. Wrong volume permissions?

This is known and because the upstream Maven image changed its behavior and required a minor change to BaseX' Dockerfile. As we cannot easily change Dockerfiles for old builds, we have a semi-broken image.

Are we forced to upgrade, or there is a workaround for this?

Several workarounds have been discussed on the mailing list some weeks ago:

The patch of course only applies to newly tagged BaseX tags and the master branch -- the old images will remain broken. For those, both the proposed `--entrypoint=basexhttp` or `--env=MAVEN_CONFIG=/srv/.m2` will provide a workaround. For derived Docker images, I'd add those three lines to the derived Dockerfile:

VOLUME ["/srv/.m2"]
ENV MAVEN_CONFIG=/srv/.m2
RUN mkdir /srv/.m2 && chown basex /srv/.m2

I'm a little bit disappointed that such changes breaking compatibility are introduced in the Maven image... The only solution would be to retag all the "dockerized" BaseX releases after cherry-picking the fix, I don't think that this is worth the effort. Most people will rely on the newest releases or git HEAD anyway.

So choose any of those runtime options or add the required lines to your Dockerfile derived from BaseX. If you don't succeed, get back to me.

I suspect this is connected to the changes made here: https://github.com/BaseXdb/basex/pull/1347/files

Actually, this was the fix for newer builds.

I'm sorry for the inconvenience -- we can't really do anything about the old releases.

Regards, Jens