Database keeps crashing about docker HOT 8 CLOSED

I'm experiencing this exact error on a Raspberry Pi 3b+ running Raspbian Lite.

from docker.

I am experiencing the same issue. I think this could be the problem with connection between monica container and db container. I also would appreciate any help. I am using SYNOLOGY NAS with portainer.

from docker.

@asbiin Can I kindly ask you if you can help us with this issue? I really would like to use Monica but still I am unable to run any docker version using the examples.
Thank you in advanced

from docker.

Could the problem be the mysql version?
most of the examples mention mysql:5.7

from docker.

I am having the same issue where the database crashes on InnoDB initialization, resulting in a loop for the database service.
Although Instead of an "Upgrade not supported", I am getting this error instead:

[System] [MY-013576] [InnoDB] InnoDB initialization has started.
[ERROR] [MY-012960] [InnoDB] Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.
[ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
[ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
[ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
[ERROR] [MY-010119] [Server] Aborting

I am following the guide Running the image with docker-compose (Apache version).

from docker.

Hello. Sorry, I don't know why this happens, but it's not related to monica. I also tested it, and the mysql container needs some time to startup, and indeed restart multiple times, but it eventually works.
Have you experienced the same issue with a mariadb container? It's 100% compatible, and might solve it.

from docker.

Hello. Sorry, I don't know why this happens, but it's not related to monica. I also tested it, and the mysql container needs some time to startup, and indeed restart multiple times, but it eventually works.

Thanks for the response. After some time and more digging, I found a working solution with mysql. It seems that the documentation for the docker-compose.yml may need some updates. What fixed my issue in particular was changing the volume name for the db container from mysql to mysqldata Here is my docker-compose.yml for those that want a simple working solution: mysql db, apache server, and no reverse-proxy:

services:
  app:
    image: monica:apache
    depends_on:
      - db
    ports:
      - *desired_port*:80
    environment:
      - APP_ENV=production
      - APP_ENV=local
      - DB_HOST=db
      - DB_DATABASE=monica
      - DB_USERNAME=monica
      - DB_PASSWORD=secret
      - LOG_CHANNEL=stderr
      - CACHE_DRIVER=database
      - SESSION_DRIVER=database
      - QUEUE_DRIVER=sync
      - APP_DISABLE_SIGNUP=false
    volumes:
      - data:/var/www/html/storage
    restart: always

  db:
    image: mysql:8.0
    environment:
      - MYSQL_RANDOM_ROOT_PASSWORD=true
      - MYSQL_DATABASE=monica
      - MYSQL_USER=monica
      - MYSQL_PASSWORD=secret
    volumes:
      - mysqldata:/var/lib/mysql
    restart: always

volumes:
  data:
  mysqldata:

Also, unrelated to this issue, monica was forcing https, so I found a solution to change APP_ENV from production to local and I have no issues running it.

Have you experienced the same issue with a mariadb container? It's 100% compatible, and might solve it.

I will try mariadb in the future, as I have monica running fine, for now. Thank you, again.

from docker.