Open progrium opened 10 years ago
Hi progrium, What is the practical use of running the web server from a Docker container? Do you expect the users to have the webapp listening on IP addresses other than the localhost? If so, exposing the raw contents of /proc to other (unauthenticated) hosts is a significant security risk.
That's really up to the user. The use is for internal, so either localhost or an internal IP. Also, running inside a container gives you a fairly limited version of /proc anyway, so you don't actually get full access to /proc, but enough for basic system introspection.
On Sun, Aug 3, 2014 at 1:09 PM, Federico Ceratto notifications@github.com wrote:
Hi progrium, What is the practical use of running the web server from a Docker container? Do you expect the users to have the webapp listening on IP addresses other than the localhost? If so, exposing the raw contents of /proc to other (unauthenticated) hosts is a significant security risk.
— Reply to this email directly or view it on GitHub https://github.com/pmuller/procfs/pull/14#issuecomment-50987715.
Jeff Lindsay http://progrium.com
I strongly disagree with adding a dockerfile to this python module, I use procfs just for parsing the /proc directory in python. This seems not related to the module and more of a personal preference. How will this benefit the users currently?
I've added a Dockerfile with a start script to either run the web server or use in CLI mode.
I've also included a markdown readme that should work just like the RST version. Pretty sure it will work with PyPI, but if not, I left the original intact. Github will use the markdown version.