This message was deleted.
# general
a
This message was deleted.
h
-> #C0200L1N1MM
m
I have the similar issue, when starting Rancher Desktop (RD) as part of Azure pipeline. RD starts with administrator acc, but Azure user fails to. I have found a workaround: • Start RD as Administrator, wait unwill completely loaded. • Exit rancher, wait for RD processes to finish. • Now Start Azure pipeline. Unfortunately this workaround stopped working for me. I'm looking for other solutions... If RD is started with Admin acc, Azure user can't get access to processes rdctl as well as to docker commands, complaining that process is started with different user. Is there a way to start RD from admin account, but grant access to process to every user who has access to Windows Server 2022?