Yup, anybody running this method (which includes me!) can expect to be doing this every year.
I completely started from scratch and still get this same error
python3.9 -m venv .
Error: Command ‘[’/srv/homeassistant/bin/python3.9’, ‘-Im’, ‘ensurepip’, ‘–upgrade’, ‘–default-pip’]’ returned non-zero exit status 1.
using this guide
What folder are you in when that error occurs?
Is that folder empty when you ran it, or are you running it from the location of an existing venv?
this is from bare metal install so it built the dirs as I went
What folder are you in when that error occurs?
cd /srv/homeassistant
is the line right before that so I going to guess the homeassistant folder
Then please do:
ls -ald
in the homeassistant folder?
In the folder you’re running the pip command in
homeassistant@raspberry:/srv/homeassistant $ ls -ald
drwxr-xr-x 5 homeassistant homeassistant 4096 Nov 7 14:33 .
homeassistant@raspberry:/srv/homeassistant $
That looks ok. Let’s try:
ls -al
df -i .
df -h .
homeassistant@raspberry:/srv/homeassistant $ ls -al
total 24
drwxr-xr-x 5 homeassistant homeassistant 4096 Nov 7 14:33 .
drwxr-xr-x 3 root root 4096 Nov 7 14:33 …
drwxr-xr-x 2 homeassistant homeassistant 4096 Nov 7 14:33 bin
drwxr-xr-x 2 homeassistant homeassistant 4096 Nov 7 14:33 include
drwxr-xr-x 3 homeassistant homeassistant 4096 Nov 7 14:33 lib
-rw-r–r-- 1 homeassistant homeassistant 75 Nov 7 14:37 pyvenv.cfg
homeassistant@raspberry:/srv/homeassistant $ df -i .
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda1 1835008 189569 1645439 11% /
homeassistant@raspberry:/srv/homeassistant $ df -h .
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 28G 5.9G 21G 23% /
homeassistant@raspberry:/srv/homeassistant $
Looks like you have a venv there already
only because I tried to install home assistant and it failed
Not much more I can suggest to be honest. If that folder was empty before you ran pip then there’s no obvious issue in what you posted.
I will once again delete that VM and build yet another one and trying again
Thanks for responding I will post what I find if I muck my way through this issue
I was afraid of that answer 
In any case users should follow the best practice:
- never update a stable running system when its ok for your needs
- if developers urge you to do so alway keep a copy of your previous install
For now I am still tempted always to download the latest HA version until, maybe, my mysterious iPad bug Cannot load Web Frontend on one iPad
is resolved. Installing a new python version is a piece of cake compared to that
that is the advantage of running VM I can update a whole new machine without messing with my production machine until I am confident that it will work as intended
still the same error
homeassistant@raspberry:/srv/homeassistant $ python3.9 -m venv .
Error: Command ‘[’/srv/homeassistant/bin/python3.9’, ‘-Im’, ‘ensurepip’, ‘–upgrade’, ‘–default-pip’]’ returned non-zero exit status 1.
homeassistant@raspberry:/srv/homeassistant $
ok after mucking around in this whole thing it is apparently not a good idea changing the default of the python to the newer version when installing python3.8/3.9 Home assistant straight up does not like that it will not build the bin folder because it locks itself out of that the home assistant folder