You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pm2-docker logs to the ~/.pm2/logs/ directory using the files app-error-0.log and app-out-0.log
Inside of a Docker container, it makes sense to leave log drivers, and more importantly log rotation to the Docker engine.
This means that even if someone uses log rotation at the docker level, PM2 log management would have to be configured within the container
Suggested fix:
Either default to --output NULL --error NULL
Or support the arguments in pm2-docker, and make a note somewhere in documentation
How could we reproduce this issue?
Run a docker container using pm2-docker. Be sure your app logs to stdout.
Exec into the running container: docker exec -it <CONTAINERNAME> bash
Change into the logs directory: cd ~/.pm2/logs
Check file size: du -h *
Seeing anything but 0's there means that PM2 will continue to use up disk space from within the container
The text was updated successfully, but these errors were encountered:
@t3h2mas are you using Linux ?
cause in my case no log file are creating by pm2-docker command..
but if i do pm2-start app.js then log files are creating in given path (im using windows 10)
What's going wrong?
pm2-docker
logs to the~/.pm2/logs/
directory using the filesapp-error-0.log
andapp-out-0.log
Inside of a Docker container, it makes sense to leave log drivers, and more importantly log rotation to the Docker engine.
This means that even if someone uses log rotation at the docker level, PM2 log management would have to be configured within the container
Suggested fix:
Either default to
--output NULL
--error NULL
Or support the arguments in
pm2-docker
, and make a note somewhere in documentationHow could we reproduce this issue?
Run a docker container using
pm2-docker
. Be sure your app logs to stdout.Exec into the running container:
docker exec -it <CONTAINERNAME> bash
Change into the logs directory:
cd ~/.pm2/logs
Check file size:
du -h *
Seeing anything but 0's there means that PM2 will continue to use up disk space from within the container
The text was updated successfully, but these errors were encountered: