3 ms·
> A common mistake for people using this base image is to install Python again, by using Debian’s version of Python Is that really a common mistake?
by monkpit 6y ago
> A common mistake for people using this base image is to install Python again, by using Debian’s version of Python
Is that really a common mistake?
- JulianWasTaken 6y ago16,328 results just on GitHub, though it fluctuates on refresh, and some are commented out: https://github.com/search?q=%22from+python%3A%22+apt-get+install+python3-dev&type=Code https://github.com/search?q=%22from+python%3A%22+apt-get+ins... (And there's likely what to clean up in the search query to make it filter more irrelevant results). Seems like though "yes" is the answer.
- digitallogic 6y agoWhoa boy, is it ever, but maybe not for the reason you're thinking. ie it isn't caused by people typing `apt-get install python`. There are many packages that have Python as a dependency these days. For example, on my Ubuntu system: > ~$ apt-cache rdepends python|wc -l > 4649 I think the best illustration of how this can happen is installing postgres libraries needed to build the psycopg2 PG client. If you know to install `libpq-dev` then you're great. But if you do something that on the surface feels totally reasonable, like installing the `postgresql-client` package... guess what? You just installed another Python interpreter. edit: formatting
- itamarst 6y agoBeyond the other two answers, I added this bit because I keep seeing people make this mistake in their StackOverflow questions about why their Dockerfile isn't working.