It's an Ubuntu bug, not Python3. Install Python3 from python.org an everything is fine, except then apt-get of cause won't give you the bug fixes.
(Other comments suggest that there are fundamental problems with Python and virtualenv and Ubuntu, so either I just fortuitously missed all of that or maybe I was in such a happy delirium of tinkering that I've now forgotten all about it.)
sudo apt-get install python-virtualenv python3
virtualenv -p/usr/bin/python3 <venv>
Yes, it'd be way cooler if -mvenv wasn't crippled in Ubuntu, but this still works fine.The issue seems to rise from a missing ensurepip module. I fixed this by just downloading the Python 3.4 sources, unpacking them and copying the unpacked lib/ensurepip/ to /usr/lib/python3.4/ after which python3 -m venv seems to work fine.
What do you mean? virtualenv exists exactly so that your libs are installed in your local directory and not globally in the system. I'm not sure how it could result in broken mess in the system that way.
docker pull python:2.7
docker pull python:3
For more granular tags: https://registry.hub.docker.com/_/python/
Either way you are hand installing a lot of packages.