Nginx-proxy-manager: Mariadb

[raidoo9]

Using Docker for Desktop on Win 10, when composing this:

db:
image: jc21/mariadb-aria:10.4
restart: always
environment:
MYSQL_ROOT_PASSWORD: "npm"
MYSQL_DATABASE: "npm"
MYSQL_USER: "npm"
MYSQL_PASSWORD: "npm"
volumes:
- ./data/mysql:/var/lib/mysql

I get this an error and the container won't run:

The Auto-extending innodb_system data file './ibdata1' is of a different size 0 pages than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!

However when composing this, no errors, container runs fine and I can log into NPM:

db:
image: 'mariadb:latest'
restart: always
environment:
MYSQL_ROOT_PASSWORD: "npm"
MYSQL_DATABASE: "npm"
MYSQL_USER: "npm"
MYSQL_PASSWORD: "npm"
volumes:
- ./data/mysql:/var/lib/mysql

Can NPM work pulling mariadb from official repo or does it need to come from yours?

[miguelwill]

yes, it can work with original images of mariadb, or bitnami, etc
in my case I have a 2-system cluster with the master-slave function using the bitnami image, which works without problems

[ionred]

For anyone else with this problem, I came across this as well. The latest mariadb even caused this error for me. I ended up pinning mariadb:10.2 and it worked like a charm

[jc21]

Also try jc21/mariadb-aria:10.4.12 as it should forcibly disable innodb.

[maltokyo]

is the official mariadb docker image supported? I would prefer to use that for long term support needs. Any reason why we "need" to go for jc21/mariadb-aria?

[miguelwill]

yes, with the official mariadb as with the bitnami version with replication, so it should work with other mysql/mariadb implementations (with or without the docker, in the configuration file the connection host is indicated)

[maltokyo]

Thanks!