-
Notifications
You must be signed in to change notification settings - Fork 179
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
[bug] docker container killed and not work #44
Comments
Could you provide additional logs? |
@yuvalsteuer Can you give some more hints? |
That is google > Could you provide additional logs? |
@songhn233 I meant, try not censoring with ... the preceding logs? just censor sensitive information |
I mentioned the specific behaviour above. Following the installation steps in the readme, every shell command returns the correct result, and finally, running
The actual behaviour is that the container crashes and exits after a period of time after starting, and the service is unavailable during this time (trying to access port 4000 directly with curl fails to make a connection). At the same time, there is no additional effective error output in I am not sure what is meant by "additional logs" or "sensitive information". If debugging is required, I can provide the server's distribution version, the results of certain diagnostic scripts, or run some commands inside the container. Alternatively, specific error stacks can be located using logId or other methods. However, no effective information is currently available. |
@songhn233 how much RAM is available on the system? I have found instances of this "Killed" message coming up because the container is consuming all of the available memory. |
@yuvalsteuer Same error:
|
Hey, I tried to run the application on a ubuntu server, using the command:
But port 80 cannot be accessed, and it will automatically exited for a period of time.
However, there is no additional information in the log that would facilitate debugging. If there are other means to aid diagnosis, I can provide assistance.
The text was updated successfully, but these errors were encountered: