-
Notifications
You must be signed in to change notification settings - Fork 0
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
Crashes with traefik after 10-15 mins with exit code 137 and no other error in logs #2
Comments
I appreciate you following up with this issue! I've made quite a few changes in the documentation and pushed out a new image. There were several errors with the example compose projects which I've fixed. The container runs as an unprivileged user now. Try pulling down a fresh image |
@gravityfargo sounds promising, I've updated with the unprivileged user and ive given the latest image a try, but it still crashes out after 10-15mins Could you update the entrypoint.sh file to run the index.js in production mode without source maps?
You could still support dev mode by setting Another option is to use |
NODE_ENV is inherited from the stock pds container . The modified code from that is used in my base image If I exec in to a test container and
If you download a copy of entrypoint.sh, make it executable, and mount it and remove the sourcemap flag. volumes:
- ./config:/pds
- ./entrypoint.sh:/entrypoint.sh You can make changes as needed. npm is still installed so you can do which I've tested to work npm install -g nodemon
nodemon index.js |
Cool ive made a custom entrypoint.sh and with nodemon, still seems to crash, I've raised a seperate bug issue here on bluesky pds bluesky-social/pds#179 |
Have tried running via Traefik, seems to work but crashes after 10 minutes with exit code 137 and no other error in logs
Running on Docker Swarm with single replica, error messages to why the container failed:
State | failed State Message | started Error message | task: non-zero exit (137)
State | failed State Message | starting Error message | No such container: pds_pds.1.t4py6tckd64immy2o2wety4xt
List of containers recently failed and running with timestamps:
The text was updated successfully, but these errors were encountered: