You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not really a question but more like a help for future users that stumble on self hosting with unraid:
Currently the docker setup uses named volumes which are not available in the unraid web ui (bind mounts are preferred there).
I had the following issue when trying to use an Unraid path: ActiveRecord::StatementInvalid: SQLite3::CantOpenException: unable to open database file (ActiveRecord::StatementInvalid)
I had to create the "/mnt/user/appdata/fizzy" folder and set the correct permissions on it before I could start the container from the web interface.
Starting the container once again solved the problem.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Not really a question but more like a help for future users that stumble on self hosting with unraid:
Currently the docker setup uses named volumes which are not available in the unraid web ui (bind mounts are preferred there).
I had the following issue when trying to use an Unraid path:
ActiveRecord::StatementInvalid: SQLite3::CantOpenException: unable to open database file (ActiveRecord::StatementInvalid)I had to create the "/mnt/user/appdata/fizzy" folder and set the correct permissions on it before I could start the container from the web interface.
Starting the container once again solved the problem.
Beta Was this translation helpful? Give feedback.
All reactions