Skip to content
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

Cant start docker image #59

Closed
simonhauck opened this issue Jul 16, 2021 · 5 comments
Closed

Cant start docker image #59

simonhauck opened this issue Jul 16, 2021 · 5 comments

Comments

@simonhauck
Copy link

Hello,

i tried to run your project as docker container with the following command docker run -p 3001:3001 louislam/uptime-kuma on an x86_64 Ubuntu 20 server. Unfortunately i can't get it up and running. The following error occurs and the service cant be reached at all:

Connect to Database

Load JWT secret from database.

(node:20) UnhandledPromiseRejectionWarning: Error: SELECT COUNT(*) FROM `user`  limit 1 - SQLITE_CORRUPT: database disk image is malformed

(Use `node --trace-warnings ...` to show where the warning was created)

(node:20) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)

(node:20) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

This error occurs for the latest version as well as version 1. Does anybody else have this issue and can it reproduce it?

@NiNiyas
Copy link
Contributor

NiNiyas commented Jul 16, 2021

Same as #51 .

@louislam
Copy link
Owner

louislam commented Jul 16, 2021

I am still investigating what possible can causes the sqlite db corrupted. I suspected that I did not implemented graceful shutdown for the current release, but still not sure.

You may try to use another volume or delete the kuma.db, see if the error still occur.

@simonhauck
Copy link
Author

After deleting the kuma.db file it worked and started successfully, thanks 👍 !
I retested it multiple times, the error occurs, at least for me, after every fresh installation. So just using creating a new container with a new volume is not enough :)

@louislam
Copy link
Owner

added graceful shutdown in 1.0.5, hopefully fixed this problem.

@simonhauck
Copy link
Author

Tested it on my system and works like a charm 👍 Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants