mammoth-forest-70320
05/03/2023, 3:21 PMwsl.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?rapid-eye-50641
05/03/2023, 4:24 PM%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 ?mammoth-forest-70320
05/03/2023, 4:25 PM\provisioning
rapid-eye-50641
05/03/2023, 4:26 PMmammoth-forest-70320
05/03/2023, 4:26 PMrapid-eye-50641
05/03/2023, 4:35 PMmammoth-forest-70320
05/03/2023, 4:36 PM/
that was causing the issuerapid-eye-50641
05/04/2023, 8:58 PMmammoth-forest-70320
05/15/2023, 11:07 PM