rancher-desktop
rancher-desktop copied to clipboard
rancher-sandbox
Standard output and Standard error are not being written unless docker is invoked with -i.
Actual Behavior
In WSL only, Standard output and Standard error are not being written unless docker is invoked with -i. I have tried from within several distros: Ubuntu 22, 20, 18, Kali.
Steps to Reproduce
Must be run in a WSL distro:
docker run -i --rm alpine echo "why do I need to add -i to get my output? This makes rancher-desktop on WSL unusable"
docker run --rm alpine echo "why do I need to add -i to get my output? This makes rancher-desktop on WSL unusable"
Result
Expected Behavior
Rancher-Desktop on Mac shows the output. Rancher-Desktop on Windows from inside a CMD prompt shows proper output Rancher-Desktop on Windows w/ nerdctl & containerd backend shows the output Docker-Desktop on Windows shows the output. Docker on Linux shows the output.
mac
git bash(zsh)
cmd
Additional Information
Ubuntu 22 in WSL
Rancher Desktop Version
1.6.0
Rancher Desktop K8s Version
1.24.6
Which container engine are you using?
moby (docker cli)
What operating system are you using?
Windows
Operating System / Build Version
Windows 10 Enterprise 21H2
What CPU architecture are you using?
x64
Linux only: what package format did you use to install Rancher Desktop?
No response
Windows User Only
No response
I'm sorry, this issue somehow got lost in the migration to the non-legacy Github projects. 😞 I thought we were tracking it on the new board already, but it seems like I mixed it up with the (related) #2094 issue.
Unfortunately, with summer vacations and other unexpected absences there is no way to get this dealt with in time for the 1.10 release, but I've added it to the 1.11 milestone now.
@jandubois I see you initially planned this for 1.11 but now removed it from the 1.13 milestone - What is the plan here? Adding args via docker run might work in a normal setting but not with predefined docker-compose files and this makes working with the WSL integration pretty annoying
I see you initially planned this for 1.11 but now removed it from the 1.13 milestone
That's because there is nobody available to work on it in the 1.13 timeframe. We seem to always get a bit overambitious with our milestones and end up removing issues again as time goes on.
The big issue though is that 2 people already tried to fix it, but could not get it to work. 😞 So it's not something you can plan to do in a day or so.
I definitely want this fixed, but I can't make any promises on when that will happen.
I hope this will be soon solved. I get bitten it in perl plugin for idea. I try to solve it with fixing there but that seems wrong ... https://github.com/Camelcade/Perl5-IDEA/pull/2836
Hi @jandubois, I would like to get that fixed too and I hoped that it would have been done in 1.13 already! Thank you
I hoped that it would have been done in 1.13 already
Yeah, me too, but unfortunately we didn't have anybody available to work on it. It won't be fixed in 1.14 either, sorry!