> Our first attempt to make sudo pip safe on Fedora [0] was This seems to be using "Fedora" to mean a *host* system, and I'd agree there. I'll note as an aside that the other host system management tool we use in Fedora is rpm-ostree, part of Atomic Host: https://github.com/projectatomic/rpm-ostree Due to the read-only bind mount over /usr provided by the ostree layer, pip fails today: # rpm-ostree status State: idle Deployments: ● fedora-atomic:fedora-atomic/25/x86_64/docker-host Version: 25.89 (2017-03-26 21:04:50) Commit: 6a71adb06bc296c19839e951c38dc0b71ee5d7a82262fef9612f256f0c2a70da OSName: fedora-atomic # pip install markdown2 ... error: [Errno 30] Read-only file system: '/usr/lib/python2.7/site-packages/markdown2.py' Which is expected, and IMO a good thing. (Although I'm a bit surprised that we ship /usr/bin/pip in AH...but that's another issue) Now, I myself use `sudo pip install` in some of my *containers*. And if something were to break there, it's much less of a big deal, I tend to recreate them from scratch periodically anyways. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
