> A pretty easy move you say?  So how would we get uwsgi to start a
> container for each vassal worker?


Sorry, i was referring to the chroot/bindmounts procedure, managing docker
instances with the Emperor is possible using the --emperor-proxy trick,
but i find it really ugly (basically the vassal first calls docker run and
then the docker instances reconnect-back to the Emperor).

Honestly i have still not found an elegant way to integrate both, this is
why (as we already have the namespace/cgroup integration implemented) we
choose (for now) to invest on dockstrap and directly use docker images
(and stop building our own images that is a really annoying and
error-prone task)


-- 
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to