-
-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raspberry Pi - incorrect sqlite architecture detected #1208
Comments
If you had done a search on existing issues you would have found similar cases. Your docker install is probably messed up, happens s lot with raspberry pi now running in 64 bits but still having x user land in 32 bits or a docker in 32 bits, which in turn pulls the incorrect image. |
I'm sorry, I did search for similar issues but I couldn't find any. Now that I searched with a better understanding of my issue I found this: #354 My OS is 32 bits, docker is 32 bits but my uname says aarch64, so if I understand correctly I should reinstall my OS and go for the 64 bits? Tank you for your help |
There's a few ways, you can either force the sqlite-jdbc library to load the 32 bits, but that's just a bandage really. The switch of raspbian from 32 to 64 bits seems to not have been very smooth for many people. Reinstalling should get everything aligned but that might be a bigger task. You can try the first solution https://github.com/xerial/sqlite-jdbc/blob/master/USAGE.md#override-detected-architecture |
Since it was a fresh install I didnt mind wiping it. I reinstalled my Raspberry Pi using the 64 bits version of Raspbian. Komga is running smoothly now. Thank you |
Steps to reproduce
I installed komga in a docker on Raspbian GNU/Linux 11 (bullseye)
Expected behavior
Accessing http://localhost:25600 from Chromium browser should open the web interface
Actual behavior
The browser says "This site can’t be reached"
Logs
Komga version
1.3.1
Operating system
Raspbian GNU/Linux 11 (bullseye)
Other details
The docker is running but I see various sql related errors in my logs. Some help would be appreciated.
Acknowledgements
The text was updated successfully, but these errors were encountered: