Well, we would use docker internally, as a way of managing the different
system images we offer our users, so it wouldn't be a matter of allowing
users to ask to run arbitrary docker images. The assumption is that we
would have the images locally.
Instead, we want to be able to run our uwsgi vassal workers from inside
docker containers, instead of just running them as regular chrooted
processes... Does that make sense?
It means we would no longer have to "roll our own" chroot templates, we
can just use docker and its aufs behind the scenes, and as a bonus we
would get all the other docker namespace stuff...
--
Harry Percival
Developer
[email protected]
PythonAnywhere - a fully browser-based Python development and hosting
environment
<http://www.pythonanywhere.com/>
PythonAnywhere LLP
17a Clerkenwell Road, London EC1M 5RD, UK
VAT No.: GB 893 5643 79
Registered in England and Wales as company number OC378414.
Registered address: 28 Ely Place, 3rd Floor, London EC1N 6TD, UK
On 11/09/14 11:49, Roberto De Ioris wrote:
I think we'd be interested in finding out what the uwsgi-docker
integration possibilities are. Saw this:
https://github.com/unbit/uwsgi-docker
I think we'd be happy with putting uwsgi in front of docker, with the
emperor controlling some vassals, and each worker running in a separate
docker container... Vassals with multiple workers could just have
multiple containers running the same image.
configuration-wise, we'd want to be able to specify:
- source image, obviously
- exported/mounted volumes from local filesystem
- memory limits and cpu shares
we're currently using unix sockets to route requests, so we'd want some
way of getting that to work, either manually using the shared volumes,
or maybe automagically...
Then uwsgi can be in charge of restarting containers if they ever die,
which would be nice...
We're at very early days of our docker exploration, so it's possible I
have totally misunderstood how everything works of course...
cheers!
HP
I do not know how much docker can be useful in the pythonanywhere context
(where you manage the system packages for the users, avoiding them to
worry about this part of the deployment process). By the way the
uwsgi-docker project could be superseeded by the more generic 'dockstrap':
https://github.com/unbit/dockstrap
you basically run
dockstrap ubuntu /foobar
and you will end with foobar containg the full rootfs of ubuntu you can
use with namespaces, chroot, pivot_root and so on
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
