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?

@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 ?

Hi! I have it in the root of

\provisioning

Ok, let me try the example provided in docs myself.

Thanks so much

Ok, the example provided in the docs did not work for me either, I am going to file a bug shortly.

I already logged: https://github.com/rancher-sandbox/rancher-desktop/issues/4595, please add anything you feel is missing

@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. 🙂