cksit
commented
4 months ago Thanks for pointing out the issue and being the first one to test the procedures. You are correct; the absolute path should be used for ansible_python_interpreter. I forgot to double-check the actual command I used in my real environment, as it has been a while since my previous installation. Additionally, new issues (requests version issue and DSM restart issue) emerged while testing in a virtual DSM yesterday.
Lastly, please feel free to create any PR, and I will be happy to accept them.
Hi. Please feel free to delete this after, I just wasn't sure of the best way to contact you through here.
Firstly, Thank you so much for going through the effort to type up your notes on this, it's really appreciated.
I was having an issue with the hosts file syntax, but worked it out now.
It may just be worth adding
ansible_python_interpreter=in front of~/path-to-your-python-virtual-env/myenv/bin/pythonin your hosts file example. I'm not sure if it is relevant but I also used python3 instead of python here. I also had to use the absolute path without ~ as for me the playbook becomes root which has a different home directory.This was due to using the command
ansible-playbook -kKi inventory/hosts setup.yml --tags=setup-all, note the -kK which asks for the SSH password, followed by the sudo password to become root in Ubuntu 20.04. I would have set up an SSH key but I had already worked out how to use the -k and -K to become sudo with the sshpass package installed. This machine is on the same LAN so not worried about security here.It seems to have just successfully finished installing so I will test it and get back to you!
P.S I would be willing to contribute to the readme to make it more detailed and easier for future readers? You obviously don't have to accept them.
Thanks so much again for all of your help!