How to set Innodb_force_recovery? about alpine-mariadb

[dominictayloruk]

Not sure, would be easier restoring from a backup.

[NaruZosa]

Except when the past fortnight of backups face the exact same issue. Restoring from a backup means losing a fortnight of prod data.

Only once the container was restarted did the issue occur, until then it acted like nothing was wrong.

[dominictayloruk]

If you create a custom config file called my.cnf and map it to /etc/my.cnf within the container, that has this within it;

innodb_force_recovery=1

Would look something like

mysql:
  image: yobasystems/alpine-mariadb
  environment:
    MYSQL_ROOT_PASSWORD: 
    MYSQL_DATABASE: 
    MYSQL_USER: 
    MYSQL_PASSWORD: 
  expose:
    - "3306"
  volumes:
    - /data/example/mysql:/var/lib/mysql
    - /data/example/my.cnf:/etc/my.cnf
  restart: always

[dominictayloruk]

Little bit more info

https://mariadb.com/kb/en/innodb-recovery-modes/

https://mariadb.com/kb/en/innodb-system-variables/#innodb_corrupt_table_action

https://bobbyiliev.com/blog/start-mysql-mariadb-recovery-mode-due-to-innodb-coruption-on-cpanel