Closed barbudor closed 12 months ago
nope
@barbudor Did a GH CI setup. Seems the Python Version is used from the Container?? Don't understand why it does not fail https://github.com/tasmota/docker-tasmota/actions/runs/4864817720
Hi @Jason2866 Not sure what your comment exactly refer too but the original problem I tried to fix is that the docker image is built as root but tasmota built is perform as user. I believe CI all run as root (but I have no experience with CI) so the install problem won't happen.
@barbudor Ahh, yes CI runs with root rights. Will have a look if it is possible to do without root.
@Jason2866 The last message above was suggesting that you would try to run the CI as non-root to check
For me there is no other way considering that the docker is built as root but executed as user: hte docker image must give all rights to user to install in /.platformio /usr/local/lib
@barbudor I checked if it is possible to do. Not really. Only with trickery and much effort. So the train stops here for CI as non root
@blakadder If you have no ohter idea, could you kindly consider to merge ?
My previous PR https://github.com/tasmota/docker-tasmota/pull/21 only partially solved the problem as the 1st ESP8266 built would still fails
Now rights are given to /usr/local/lib/python3.10/site-packages so platformio can install zopfli, tasmota_metrics and future package at the right position Still kept /.cache and /.local to prevent another warning