[GH-ISSUE #346] Mariadb #301

Closed
opened 2026-02-26 06:32:09 +03:00 by kerem · 6 comments
Owner

Originally created by @raidoo9 on GitHub (Apr 3, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/346

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?

Originally created by @raidoo9 on GitHub (Apr 3, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/346 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?
kerem 2026-02-26 06:32:09 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@miguelwill commented on GitHub (Apr 5, 2020):

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

<!-- gh-comment-id:609469358 --> @miguelwill commented on GitHub (Apr 5, 2020): 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
Author
Owner

@ionred commented on GitHub (Apr 21, 2020):

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

<!-- gh-comment-id:617409217 --> @ionred commented on GitHub (Apr 21, 2020): 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
Author
Owner

@jc21 commented on GitHub (Apr 21, 2020):

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

<!-- gh-comment-id:617458087 --> @jc21 commented on GitHub (Apr 21, 2020): Also try `jc21/mariadb-aria:10.4.12` as it should forcibly disable innodb.
Author
Owner

@maltokyo commented on GitHub (Jul 16, 2020):

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?

<!-- gh-comment-id:659266653 --> @maltokyo commented on GitHub (Jul 16, 2020): 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?
Author
Owner

@miguelwill commented on GitHub (Jul 17, 2020):

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)

<!-- gh-comment-id:659787035 --> @miguelwill commented on GitHub (Jul 17, 2020): 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)
Author
Owner

@maltokyo commented on GitHub (Jul 18, 2020):

Thanks!

<!-- gh-comment-id:660390581 --> @maltokyo commented on GitHub (Jul 18, 2020): Thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#301
No description provided.