You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
there's been a usability problem with wins for quite some time regarding the cli prc command. the idea is youre calling out to the host via grpc to execute the exe on the host. the process to do this is from a container and since this code here
this code is run in the container via cli prc and it checks the container for the binary and then calls the binary via grpc on the host meaning the binary has to be in both locations. in the container and on the host. we've basically been getting around this problem with copying files everywhere in run.ps1 powershell scripts.
proposal... add grpc logic so the cli prc command asks the host via the socket if the binary is there, is the right hash etc.
The text was updated successfully, but these errors were encountered:
there's been a usability problem with wins for quite some time regarding the cli prc command. the idea is youre calling out to the host via grpc to execute the exe on the host. the process to do this is from a container and since this code here
wins/pkg/paths/file_binary.go
Lines 11 to 42 in 3533580
this code is run in the container via cli prc and it checks the container for the binary and then calls the binary via grpc on the host meaning the binary has to be in both locations. in the container and on the host. we've basically been getting around this problem with copying files everywhere in run.ps1 powershell scripts.
proposal... add grpc logic so the cli prc command asks the host via the socket if the binary is there, is the right hash etc.
The text was updated successfully, but these errors were encountered: