Seafile Server Pro Edition w/ Docker & default docker-compose.yml won't connect to elasticsearch

I am testing a new setup of seafile docker compose and noticed the search does not work in seafile webgui.

The seafile docker install instructions provide a docker-compose.yml where elasticsearch names do not match and out of the box default settings won’t allow seafile docker to connect to elasticsearch docker. The seafile default docker-compose.yml reads

    container_name: seafile-elasticsearch

However the default config in seafevents.conf has specified

es_host = elasticsearch

So either you need to change the container_name or the seafevents.conf so that both names for elasticsearch match.

Next, when I check the elastic search logs using
docker logs --since=4h seafile-elasticsearch
the logs identify many warn messages:

{"@timestamp":"2023-12-10T00:12:26.369Z", "log.level": "WARN", "message":"received plaintext http traffic on an https channel, closing connection Netty4HttpChannel{localAddress=/, remoteAddress=/}", "ecs.version": "1.2.0","":"ES_ECS","event.dataset":"elasticsearch.server","":"elasticsearch[ddc8248f5e38][transport_worker][T#2]","log.logger":"","elasticsearch.cluster.uuid":"789SNE2ySQGYqXjEwiCCWQ","":"1gGEW77yRQmyXEsvTMhUzg","":"ddc8248f5e38","":"docker-cluster"}

According to elasticsearch
https: / / w w w
" WARN: received plaintext http traffic on a https channel, closing connection
Indicates that there was an incoming plaintext http request. This typically occurs when an external applications attempts to make an unencrypted call to the REST interface. Please ensure that all applications are using https when calling the REST interface with SSL enabled. "

Why is docker seafile communicating to elasticsearch using http and not using https?

What do I need to change to make this function correctly?

The quick fix I performed was modifying the elasticsearch container file
I suppose I could add this to the docker-compose.yml environment variable next time
elasticsearch: environment:

This setting successfully allowed seafile to connect with elasticsearch.
However I noticed that the initital document seafile-tutorial.doc that is pre-placed in a library fails to be searchable for inside text data. So I downloaded this file, deleted it from library, and then uploaded same file. Then I ran

docker exec -it seafile /opt/seafile/seafile-server-latest/pro/ search --clear
docker exec -it seafile /opt/seafile/seafile-server-latest/pro/ search --update

and then I see this error

12/10/2023 20:14:53 [INFO] seafes:181 extract: extracting 9f65d98c-12b3-4025-9e53-6b21c18d6f3b /delete_seafile-tutorial2.doc...
timeout: failed to run command ‘java’: No such file or directory
12/10/2023 20:14:53 [WARNING] seafes:185 extract: failed to extract /seafile-tutorial.doc: [Errno 32] Broken pipe
12/10/2023 20:14:53 [INFO] elastic_transport.transport:336 perform_request: GET http://seafile-elasticsearch:9200/repofiles/_doc/9f65d98c-12b3-4025-9e53-6b21c18d6f3b%2Fseafile-tutorial.doc?_source_includes= [status:404 duration:0.002s]
12/10/2023 20:14:53 [INFO] elastic_transport.transport:336 perform_request: PUT http://seafile-elasticsearch:9200/repofiles/_doc/9f65d98c-12b3-4025-9e53-6b21c18d6f3b%2Fseafile-tutorial.doc [status:201 duration:0.008s]
12/10/2023 20:14:53 [INFO] elastic_transport.transport:336 perform_request: POST http://seafile-elasticsearch:9200/repofiles/_refresh [status:200 duration:0.026s]
12/10/2023 20:14:53 [INFO] elastic_transport.transport:336 perform_request: POST http://seafile-elasticsearch:9200/repofiles/_refresh [status:200 duration:0.001s]
12/10/2023 20:14:53 [INFO] elastic_transport.transport:336 perform_request: POST http://seafile-elasticsearch:9200/repo_head/_update/9f65d98c-12b3-4025-9e53-6b21c18d6f3b [status:200 duration:0.043s]
12/10/2023 20:14:53 [INFO] elastic_transport.transport:336 perform_request: POST http://seafile-elasticsearch:9200/repo_head/_refresh [status:200 duration:0.011s]

None of the file contents of the seafile-tutorial.doc are searchable. I also did upload other .txt and .pdf file and most do successfully index and are searchable.
Why would this seafile provided seafile-tutorial.doc file be causing error? How can I troubleshoot this further?

Last, are there any other quirks or issues that should performed to stand up a fully working docker compose environment?
Is anyone using the docker compose in production and can recommend tuning any of the configuration for more performance? I can provide the machine plenty of ram and am curious how much if any performance can be gained by increasing from the defaults in the yml

entrypoint: memcached -m 256


"ES_JAVA_OPTS=-Xms1g -Xmx1g"

        soft: -1
        hard: -1
    mem_limit: 2g

Thank you!