1) A container does not need a full OS inside it, or the full OS userland files. A container does not run any OS kernel inside it. It just needs at a minimum the program(s) you are running directly + any other extra files which your programs might depend upon.
For convenience (and familiarity), you can inherit a full userland set files for any popular linux distro. Some people dont bother, others do. Often it depends on the task at hand which is best choice. Depending what are the process(es) you are running in the container. Mainly it is conveint / fastest way to easily satisfy the software's package dependancies, and libs deps, and also to use a nice pkg manager tool like APT or RPMs. Which is familiar ways. 2) The decision whether to put each service in its own individual 2-3 containers, or combine them together under 1 container is entirely your own choice. There are benefits and drawbacks to either way. Sometimes I do it one way, sometimes the other. It really depends much on the software and for what is best in the specific situation. There can be many factors to affect your decision from all sides. Such as the security, the ease of management, ease of sharing with other people, the ease of configuration. And re-usability of the components to nearby projects. Plus many other much smaller factors too. You are free to do what you think is best. Personally I use "s6-overlay" which handles all the process management within my containers. Even the single-service ones. And for running multiple services in 1 container, it makes for a very simple and effecient solution. Kind Regards On Wed, Aug 17, 2016 at 4:31 PM, Tiglath <tiglathsur...@gmail.com> wrote: > > Many thanks for taking the time to reply. > > So the difference between container and VM is that the container still > needs a full OS, but not the virtualized > hardware -- quite a saving. > > It is best then that I run Flask, DB and my app in different containers, > and they communicate through ports. > > The DB as you say should have its data repository outside the container, > where the hosts backups will include it. > > Since flask is a web framework can I run Flask and a web server in the > same container, or best in two? > > I understand that to orchestrate the various container is best to use > Compose. > > Gratitute for being so generous. > > J. > > > > -- > You received this message because you are subscribed to the Google Groups > "docker-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to docker-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "docker-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to docker-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
