This is a docker issue. I'd suggest you set up a logging driver. From a brief look it seems like this is a runtime option.

More details: https://docs.docker.com/config/containers/logging/configure/ and https://docs.docker.com/config/containers/logging/

have you seen this https://github.com/jerryhopper/fusionauth-app-multiarch ?
it's from community member @hopper-jerry and may meet your needs.

I end up using a docker image of mailcatcher.

I use the default docker-compose.yml, but use this docker-compose.override.yml:

version: '3' services: mailcatcher: image: yappabe/mailcatcher ports: - "1025:1025" - "1080:1080" networks: - mailcatcher search: image: docker.elastic.co/elasticsearch/elasticsearch:7.8.1 environment: cluster.name: fusionauth bootstrap.memory_lock: "true" discovery.type: single-node FUSIONAUTH_SEARCH_MEMORY: ${FUSIONAUTH_SEARCH_MEMORY} ES_JAVA_OPTS: ${ES_JAVA_OPTS} # Un-comment to access the search service directly # ports: # - 9200:9200 # - 9300:9300 networks: - search restart: unless-stopped ulimits: memlock: soft: -1 hard: -1 volumes: - es_data:/usr/share/elasticsearch/data fusionauth: depends_on: - search - mailcatcher environment: SEARCH_SERVERS: http://search:9200 SEARCH_TYPE: elasticsearch networks: - mailcatcher - search networks: search: driver: bridge mailcatcher: driver: bridge volumes: es_data:

Then I configure the SMTP settings to use the hostname mailcatcher and the port 1025. I can then send email and view it in the mailcatcher interface, at localhost:1080.

Here's the relevant dockerfile: https://github.com/yappabe/docker-mailcatcher/blob/master/Dockerfile

Here's more about mailcatcher: https://mailcatcher.me/

How much memory are you giving to the java process?

You can also switch to the database search engine and see if removing ES resolves the issue. At that point it might be a resource issue.

https://fusionauth.io/docs/v1/tech/tutorials/switch-search-engines/ has instructions on how to change these.

That's great to hear, glad you figured it out!

The docker compose references the latest tag, but that tag is not dynamic, it is only the latest at a point in time.

To ensure you have the most recent latest tag - you can always run this command: docker pull fusionauth/fusionauth-app:latest

This is a common point of confusion, and there are lots of opinions on it as you might imagine. For your reading pleasure:

https://vsupalov.com/docker-latest-tag/
https://blog.container-solutions.com/docker-latest-confusion

When you re-index, we delete our named index and rebuild it.

You would probably be better off creating your own index.

Check out the official documentation on using Docker + Kickstart.

A good way to test the app is up and running is to run docker logs 27e4c9edd311 where 27e4c9edd311 is the docker container id, which is found by running docker ps|grep fusionauth.

If you are using docker-compose, you can also run docker-compose logs -f fusionauth.

Look in the logs for any errors. On successful startup, you'll see this message (with perhaps a different version message):

--------------------------------------------------------------------------------------------------------- ------------------------------- Starting FusionAuth version [1.16.0-RC.1] ------------------------------- ---------------------------------------------------------------------------------------------------------