Should I use forever/pm2 within a (Docker) container?

node.js docker coreos microservices
Patrick picture Patrick · Mar 9, 2015 · Viewed 13.4k times · Source

I am refactoring a couple of node.js services. All of them used to start with forever on virtual servers, if the process crashed they just relaunch.

Now, moving to containerised and state-less application structures, I think the process should exit and the container should be restarted on a failure.

Is that correct? Are there benefits or disadvantages?

Answer

Peter Lyons picture Peter Lyons · Mar 9, 2015

My take is do not use an in-container process supervisor (forever, pm2) and instead use docker restart policy via the --restart=always (or one of the other flavors of that option). This is more inline with the overall docker philosophy, and should operate very similarly to in-container process supervision since docker containers start running very quickly.

The strongest advocate for running in-container process supervision I've seen is in the phusion baseimage-docker README if you want to explore the other position on this topic.

Related questions

docker: having trouble running npm install after creating a new user

So I have another follow-up question regarding installing a node.js-based framework under Docker on CoreOS, per this post. So, because npm is finicky about installing from package.json via root, I've had to create a nonroot sudo user in …

Read More
Docker-compose: node_modules not present in a volume after npm install succeeds

I have an app with the following services: web/ - holds and runs a python 3 flask web server on port 5000. Uses sqlite3. worker/ - has an index.js file which is a worker for a queue. the web server interacts …

Read More
Use docker run command to pass arguments to CMD in Dockerfile

I'm new to Docker and I'm having a hard time to setup the docker container as I want. I have a nodejs app can take two parameters when start. For example, I can use node server.js 0 dev or node …

Read More