This message was deleted.
# rancher-desktop
a
This message was deleted.
w
you mean docker stop?
p
No, I execute docker run (without -d) and the container start normally but if I want to stop it normally I can do a ctlr-c (at least in linux ­čśä) In windows it does not work I have to open a second powershell and do a docker kill or stop from there
w
yeah guessing thats just the reality of the container running on the other side of the sock
p
so no workaround?
w
ctrl-c is being eaten by windows vs handed through
not that i am aware of
i would say just background the run
p
yes that is the thing I'll end up doing but hoped for a better solution any idea why this happen?
w
guessing the sigint is being eaten by windows and not relayed into the VM
you could open an issue as maybe the shim could catch it and relay. Sometimes windows can be a little grabby
p
if I add -it option it seems to get the ctlr-c
w
yeah interactive vs foreground
but as you note if you run it foreground directly than it respects sigint
s
I don't think you can guarantee
ctrl-c
will stop a
docker run
without
-it
on any platform - I think it works on some platforms but I think that's undefined behaviour