It is generally recommended that you run one process per docker container. And that makes sense if you are trying to run a single web application that requires different kinds of tools.
For example, an open source web application kanboard
uses
Now, if this was the only web application that I was going to run, then it makes sense to run each tool in a separate container in order to use dockers one process per container .
But let's say, instead of launching only one web application, I wanted to run several web applications,
- kanboard
- EtherPad
- plexus
- Owncloud
- dockuwiki
- discourse
, -? , , , ,
- (mysql, postgres, sqlite)
- (memcache, redis)
- (, , RQ, SHARQ)
- - (nginx, apache)
- (lucene, sphinx, opensearchserver)
-. 2 , ,
- . kanboard, etherpad .
- dockers dictum
one process per container
mysql, postgres, sqlite, memcache .. docker linking
, . . .
, ? , ?
, , ( ) ? , -?