Closed mwLabs-eu closed 1 month ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
@Floppy is this an issue you're aware of with mariadb that requires any different/additional init steps? I'm seeing the same ActiveRecord::StatementInvalid: Mysql2::Error: Cannot drop index 'index_taggings_on_tag_id': needed in a foreign key constraint (ActiveRecord::StatementInvalid)
when testing locally.
No, I wasn't aware, but it's definitely a Manyfold bug; I'll investigate.
I've got this replicated locally, so yep, I'll take care of it.
Just released a fix for this (and another MariaDB issue I found at the same time) in v0.74.2. The linuxserver robots should get a build out soon for you; I hope it gets things up and running!
I experience the same error on a new configuration with a fresh mariadb in v0.74.2
Oh, that's not good. Same error, Mysql2::Error: Cannot drop index 'index_taggings_on_tag_id': needed in a foreign key constraint
?
For me it's working now since updating
For me it's working now since updating
I've installed it today for the first time, so I downloaded directly the latest image. The issue happens with mariadb and with sqlite too
Hm, SQLite too implies a different error, and should have been caught in our test systems which use it. Could you post the output you see?
Hm, SQLite too implies a different error, and should have been caught in our test systems which use it. Could you post the output you see?
I don't know if is related or I should open another issue, but I've seen in the logs that there is a complain about the missing secret key, but if I try to run docker run --rm -it --entrypoint /bin/bash lscr.io/linuxserver/manyfold:latest generate-secret
this is the output:
generate-secret: line 6: rake: command not found
Looks like something is broken with rake secret
; I can't make it work in the upstream container image either; Don't know how to build task 'secret'
.
Looks like something is broken with
rake secret
; I can't make it work in the upstream container image either;Don't know how to build task 'secret'
.
The correct command is bundle exec rails secret
, not rake - that should do it.
(I'm not sure why (or if) rake secret worked before, but rails secret is the right way)
OK, @AndreaPro the issue is indeed that your SECRET_KEY_BASE value is missing, it's not database related. We should probably move that to another issue (unless @thespad has already fixed it) and close this one, because the original issue seems to be fixed.
Looks like something is broken with
rake secret
; I can't make it work in the upstream container image either;Don't know how to build task 'secret'
.The correct command is
bundle exec rails secret
, not rake - that should do it.(I'm not sure why (or if) rake secret worked before, but rails secret is the right way)
You need to update your docs then :)
LOL so I do! My bad!
Done :)
OK, @AndreaPro the issue is indeed that your SECRET_KEY_BASE value is missing, it's not database related. We should probably move that to another issue (unless @thespad has already fixed it) and close this one, because the original issue seems to be fixed.
Yes, I've pushed a fix for the helper script that should sort out the secret generation.
Is there an existing issue for this?
Current Behavior
Initial Database Setup fails when using MariaDB, so the container cannot be set up.
Expected Behavior
Successful setup using Mariadb
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs