mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #1357] Missing manifest Mariadb? #1076
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1076
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aroundmyroom on GitHub (Aug 28, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1357
Pulled the new version (and this new version is also running) but it gave an error on the db part
manifest for jc21/mariadb-aria:10.4 not found: manifest unknown
Previously this was working ok.
what could I do possibly wrong or did I miss a change in a previous version?
@aroundmyroom commented on GitHub (Aug 28, 2021):
ah . version 10.4 must become :latest
solved
@aroundmyroom commented on GitHub (Aug 28, 2021):
when changing 10.4 to latest, I get again an issue on the logon, so probably the change from db goes wrong .. wierd. in combination with username/pwd
@nielsvf commented on GitHub (Aug 28, 2021):
I've got this as well.
@aroundmyroom commented on GitHub (Aug 28, 2021):
wonder what has changed betwee 2.9.3 and 2.9.8 so I rolled back an backup.
@aroundmyroom commented on GitHub (Aug 29, 2021):
the problem is an already reported issue (but that user moved to sqllite)
the storage engine InnoDB is not present when you move from 10.4 to Latest
So where I initially started with 10.4 (and that one worked before when pulling) now it tells us that the manifest is not there and changing the db to : latest gives a problem that it cannot migrate correctly.
So in this situation I do not care about the upgrade of the db and will let the error be the error and do not care about it.
@tuxmeister commented on GitHub (Aug 30, 2021):
Same issue here, just tried a pull, updated to :latest tag and pulled again, now getting the following error:
[8/30/2021] [2:03:20 PM] [Global ] › ✖ error select * from ``migrations_lock`` - ER_UNKNOWN_STORAGE_ENGINE: Unknown storage engine 'InnoDB'@fdr76 commented on GitHub (Aug 30, 2021):
it looks I have the same issue when I change 10.4 to latest.
@tuxmeister can you tell in which log-file you get the error?
@aroundmyroom commented on GitHub (Aug 30, 2021):
@fdr76 you can see this when you do not run it in daemon mode (so do not run with -d) from commandline / shell
so the version :latest is a new mysql database without InnoDB .. no clue what has changed ..
@jc21 commented on GitHub (Aug 30, 2021):
See https://github.com/jc21/docker-mariadb-aria/issues/8
use
jc21/mariadb-aria:10.4.15-innodb@nielsvf commented on GitHub (Aug 31, 2021):
It works now! Thanks for your reply. The README.md still contains
image: 'jc21/mariadb-aria:latest'though. Or is that for new installs only?@aroundmyroom commented on GitHub (Aug 31, 2021):
That fixed it. Thanks !
@jc21 commented on GitHub (Aug 31, 2021):
Yep this is fine for new installs. It's those whom had the previous image with innodb enabled that experience problems.