https://rancher.com/ logo
Title
m

mammoth-forest-70320

05/03/2023, 3:21 PM
It appears Provisioning Scripts on Windows are not being run because they cannot be found. Looking at the logs no files are found when it attempts to execute
wsl.exe --distribution rancher-desktop --exec /usr/bin/find /etc/local.d ( -name *.start -o -name *.stop ) -print -exec chmod a+x {}
. When I manually execute
wsl.exe --distribution rancher-desktop --exec /usr/bin/find /etc/local.d -name *.start -print
it finds nothing. However, when I execute
wsl.exe --distribution rancher-desktop --exec /usr/bin/find /etc/local.d/ -name *.start -print
(notice the trailing
/
) it returns the .start provisioning script. Has anyone else run into this?
r

rapid-eye-50641

05/03/2023, 4:24 PM
@mammoth-forest-70320, At what path do you have your provisioning script reside? The expected location on Windows is
%AppData%\rancher-desktop\provisioning
as per the docs .. If you are creating provisioning scripts in a sub directory under ``%AppData%\rancher-desktop\provisioning` then it could be a case Rancher Desktop doesn't handle at the moment. Any thoughts @proud-jewelry-46860 ?
m

mammoth-forest-70320

05/03/2023, 4:25 PM
Hi! I have it in the root of
\provisioning
r

rapid-eye-50641

05/03/2023, 4:26 PM
Ok, let me try the example provided in docs myself.
m

mammoth-forest-70320

05/03/2023, 4:26 PM
Thanks so much
r

rapid-eye-50641

05/03/2023, 4:35 PM
Ok, the example provided in the docs did not work for me either, I am going to file a bug shortly.
m

mammoth-forest-70320

05/03/2023, 4:36 PM
I already logged: https://github.com/rancher-sandbox/rancher-desktop/issues/4595, please add anything you feel is missing
🙌 1
I was able to address this with a local build. It seems it is the trailing
/
that was causing the issue
r

rapid-eye-50641

05/04/2023, 8:58 PM
@mammoth-forest-70320, it's good to know you got it working in a local build. Please feel free to file PR on the rancher-desktop repo with your fix. 🙂
👍 1
m

mammoth-forest-70320

05/15/2023, 11:07 PM