-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 Stops on Unraid #144
Comments
Also on Unraid, mine stops after each lookup. I'll start it and leave it unused to see if it stops on its own for me as well. |
I have really struggled to get to the bottom of this one. Web-check dies every single time it's used on unraid, I cant figure out why. |
you guys ever figure out why the container stops in unraid? |
Nope! I just cant keep it running. I've debugged as much as I could, never figured it out. :( |
add this to the extra params field in unraid: basically just restarts the container when it shuts off |
The docker container appears to stop on its own without interaction when installed on Docker/Unraid. The container needs to be manually started again.
Edit:
Here's a copy of the logs before the container shut off.
node:events:491
throw er; // Unhandled 'error' event
^
Error: connect ETIMEDOUT 8.8.4.4:443
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)
Emitted 'error' event on ClientRequest instance at:
at TLSSocket.socketErrorListener (node:_http_client:494:9)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '8.8.4.4',
port: 443
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
The text was updated successfully, but these errors were encountered: