What is the difference between nginx daemon on/off option?

nginx webserver daemon docker
KopBob picture KopBob · Sep 22, 2014 · Viewed 35.1k times · Source

This is my first web-server administration experience and I want to build docker container which uses nginx as a web-server. In all docker tutorial daemon off; option is put into main .conf file but explanation about it is omitted.

I search on the internet about it and I don't understand what is the difference between daemon on; and daemon off; options. Some people mentioned that daemon off; is for production, why?

Can you explain, what is the difference between this two options, and why I should use daemon off; on production?

Answer

johntellsall picture johntellsall · Jan 16, 2016

For normal production (on a server), use the default daemon on; directive so the Nginx server will start in the background. In this way Nginx and other services are running and talking to each other. One server runs many services.

For Docker containers (or for debugging), the daemon off; directive tells Nginx to stay in the foreground. For containers this is useful as best practice is for one container = one process. One server (container) has only one service.

Setting daemon off; is also useful if there's a 3rd party tool like Supervisor controlling your services. Supervisor lets you stop/start/get status for bunches of services at once.

I use daemon off; for tweaking my Nginx config, then cleanly killing the service and restarting it. This lets me test configurations rapidly. When done I use the default daemon on;.

Related questions

Configure nginx with multiple locations with different root folders on subdomain

I'm looking to serve the root url of a subdomain and directory of a subdomain to two different folders on my server. Here is the simple set-up that I have and is not working... server { index index.html index.htm; …

Read More
Nginx upstream prematurely closed connection while reading response header from upstream, for large requests

I am using nginx and node server to serve update requests. I get a gateway timeout when I request an update on large data. I saw this error from the nginx error logs : 2016/04/07 00:46:04 [error] 28599#0: *1 upstream prematurely closed connection while reading …

Read More
Using variables in Nginx location rules

In Nginx, I'm trying to define a variable which allows me to configure a sub-folder for all my location blocks. I did this: set $folder '/test'; location $folder/ { [...] } location $folder/something { [...] } Unfortunately, this doesn't seem to work. While Nginx …

Read More