docker-mailserver: [BUG]: Solr image is oudated and does not support arm64

๐Ÿ“ Preliminary Checks

  • I tried searching for an existing issue and followed the debugging docs advice, but still need assistance.

๐Ÿ‘€ What Happened?

When following the documentation on setting up full test search the following docker image is used for the setup: https://hub.docker.com/r/lmmdock/dovecot-solr

This image hasnโ€™t been updated in 2 years and does not support the arm64 architecture supported by DMS.

I think that the official image should be used instead.

๐Ÿ‘Ÿ Reproduction Steps

  1. Use an arm64 server
  2. [Follow the documentation] on setting up Solr full text indexing
  3. See exec /opt/docker-solr/scripts/docker-entrypoint.sh: exec format error in the Solr container logs
  4. See that the image is 2 years old and doesnโ€™t support arm64

๐Ÿ‹ DMS Version

v13.1

๐Ÿ’ป Operating System and Architecture

Debian GNU/Linux 11 (bullseye) aarch64

โš™๏ธ Container configuration files

solr:
    image: lmmdock/dovecot-solr:latest
    volumes:
      - ./docker-data/dms/config/dovecot/solr-dovecot:/opt/solr/server/solr/dovecot
    restart: always

๐Ÿ“œ Relevant log output

exec /opt/docker-solr/scripts/docker-entrypoint.sh: exec format error

exec /opt/docker-solr/scripts/docker-entrypoint.sh: exec format error

exec /opt/docker-solr/scripts/docker-entrypoint.sh: exec format error

exec /opt/docker-solr/scripts/docker-entrypoint.sh: exec format error

exec /opt/docker-solr/scripts/docker-entrypoint.sh: exec format error

exec /opt/docker-solr/scripts/docker-entrypoint.sh: exec format error

exec /opt/docker-solr/scripts/docker-entrypoint.sh: exec format error

exec /opt/docker-solr/scripts/docker-entrypoint.sh: exec format error

exec /opt/docker-solr/scripts/docker-entrypoint.sh: exec format error

exec /opt/docker-solr/scripts/docker-entrypoint.sh: exec format error

Improvements to this form?

Suggested fix?

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 1
  • Comments: 17 (15 by maintainers)

Most upvoted comments

I understand. I just thought that wonโ€™t fix was a better description than Resolved (as we did not resolve it but nuked it out of existence to avoid resolving it)

Nuking it is, for me, a way of resolving it ๐Ÿ˜‰

I understand. I just thought that wonโ€™t fix was a better description than Resolved (as we did not resolve it but nuked it out of existence to avoid resolving it)

This sort of thing can happen with community contributed content and features unfortunately.

Thereโ€™s no way around that sadly. But at least this way what community uses the community maintains so the new cool things work while the old ones are dropped. Like you said updating my chagnelog:

If you use Solr, support can be restored if youโ€™re willing to contribute docs for the feature that resolves the concerns raised.


Iโ€™ll go ahead and close this as Wonโ€™t Fix before the PR closes it as Fixed. Someone may get the false sense of the issue being solved and look for a solution in the comments.

Iโ€™m open to dropping the docs page

Iโ€™ve made a PR dropping Solr: #4025

Seems like Xapian is working and K9Mail just cannot search text.

I just tried using the official image instead and I get some errors from DMS:

May 20 11:03:44 f9b1fdbc38a6 dovecot: indexer-worker(jiri@stefka.eu)<1215><1/B0+t4YAsFdWWg7:6PfOEfARS2a/BAAAMN9mZQ>: Error: fts_solr: Lookup failed: 404 Not Found

May 20 11:03:44 f9b1fdbc38a6 dovecot: indexer-worker(jiri@stefka.eu)<1215><1/B0+t4YAsFdWWg7:6PfOEfARS2a/BAAAMN9mZQ>: Error: Mailbox Archive: Status lookup failed: Internal error occurred. Refer to server log for more information. [2024-05-20 11:03:44]

Iโ€™ll look into what needs to be changed in the config.