This message was deleted.
# rancher-desktopa
adamant-kite-43734
06/21/2022, 4:38 PMThis message was deleted.
r
ripe-traffic-25731
06/21/2022, 4:41 PMDoes anyone has an idea what's going wrong there? I've already tried a factory reset and cleaned up all the old docker stuff.
p
proud-jewelry-46860
06/21/2022, 4:42 PMHmm, it sounds like there's an issue in cross-WSL-distro functionality 😞
r
ripe-traffic-25731
06/21/2022, 4:43 PMIs it possible, that the path does exist temporarily in wsl rancher-desktop but not in my wsl ubuntu and the search paths are somehow broken?
ripe-traffic-25731
06/21/2022, 5:01 PMOkay, this is apparently not the case. Btw, I've also checked this one: https://github.com/docker/for-win/issues/8781
ripe-traffic-25731
06/21/2022, 5:02 PMAnd I've also tried the minimal compose example from the docker compose docs.
w
wide-mechanic-33041
06/21/2022, 5:56 PMand https://github.com/rancher-sandbox/rancher-desktop/issues/1431. Using docker-compose w moby/docker worked from the same working directory.
r
ripe-traffic-25731
06/21/2022, 5:57 PMYes, I saw this. It might be related.
ripe-traffic-25731
06/22/2022, 8:31 AMIs anyone facing similar issues?
ripe-traffic-25731
06/22/2022, 1:52 PMIt is definitely a WSL issue, since in the Powershell of the host system everything works fine. 😕
ripe-traffic-25731
06/22/2022, 1:53 PMThere is something fundamentally broken with path handling in WSL.
w
wide-mechanic-33041
06/23/2022, 11:44 AMGuessing not WSL, but the shim running in the host not passing the cwd correctly to the WSL side
👍 1
69 Views