-
-
Notifications
You must be signed in to change notification settings - Fork 147
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
docker container could not be started #296
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
what's the output of did you deploy this container with the docker run above or did you use synology's ui to do so? is your db in /books or /config? |
uname -mr && docker version
did you deploy this container with the docker run above or did you use synology's ui to do so?
is your db in /books or /config? what is the filesystem of /volume5
Thank you. |
I mean, specifically, the metadata.db
this could be or be part of your problem. What is the output of
it's also worth noting that this kernel has been end of life since February 3rd, 2022 |
Thank you. after updating docker container to the newest version, the app seems to be operational. |
Is there an existing issue for this?
Current Behavior
Hello
I am using synology docker. and the calibre-web container worked well until recent.
It was stopped unexpectedly.
I tried updating to the newest version and did not help.
Expected Behavior
No response
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: