On Sun, Nov 9, 2014 at 7:28 AM, Vladimir Mosgalin
<[log in to unmask]> wrote:

> As for more complex way to use containers, e.g. as lightweight
> virtualization to get new network namespace and resources control for a
> certain group of services, docker is unsuitable and will probably ever
> be. Docker seems to be designed with concept of isolating single
> services in mind; it's not always the usage case.
>
> E.g. we had a goal "use SL7 on database host, but run PostgreSQL with
> some related services inside SL6 container, until we get enough time to
> make it work on SL7 natively (after which we'll move it from container
> to base system)".
> Having nearly complete virtual host with sshd, postgresql server and
> related tools would be cumbersome in docker. This task can be solved
> with LXC, however.

Out of curiosity: what was the problem? I'd assume that SSH, for
remote configuration management inside the container, and the actual
running service itself inside the container, would be common
configurations.