> Some more questions regarding the approach with running uwsgi > --setns-socket inside docker. > > - it seems 2 uwsgi processes are created when doing "uwsgi > --setns-socket". > Is it possible to launch only one to minimize the memory footprint? > - also, if the absolutely core and minimal uwsgi here is needed, what's > the > way to compile it for minimal memory footprint? > > - > [uwsgi] > setns=/foobar/join.me > http=:8080
in 2.0.1 (from github) you only need setns-socket (no need to bind workers) and only the master will be spawned (in the docker container). Than you attach from the vassal with --setns. For networking, if you do not want to rely on docker network bridge you can use shared sockets, but then we are again using docker only for the rootfs layers and this seems a bit overkill to me (but i could be wrong obviously) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
