Open MrLuje opened 2 years ago
Thanks for the bug report! I was able to reproduce this on Windows 10 Pro 10.0.19044 Build 19044, both on RD 1.3.0 and on a dev build off of 4d379284. This is something that should be working. We'll try to get to it when we have a chance, though PRs are always welcome :)
Anyone able to fix this issue? Experiencing the same issue with
I, too, am running into this, very similar specs to @kwuite.
I'm now also having this issue while using VSCode devcontainers feature
failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting \"/mnt/wsl/rancher-desktop/run/docker-mounts/9d4b57e3-7f96-4f1e-9d21-a013a512186d\" to rootfs at \"/tmp/vscode-wayland-9658b5aa-bb1b-4ac5-abee-4e15ad8f8d05.sock\": mount /mnt/wsl/rancher-desktop/run/docker-mounts/9d4b57e3-7f96-4f1e-9d21-a013a512186d:/tmp/vscode-wayland-9658b5aa-bb1b-4ac5-abee-4e15ad8f8d05.sock (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
Rancher Desktop 1.8.1
Hi @adamkpickering, just want to make sure this bug has not been forgotten If not, I can try to look at it but I'll probably need a few leads to start looking from the right place
Hi @MrLuje, unfortunately the dev team is quite busy - a fix is not scheduled for inclusion in 1.11, which is scheduled for release around the end of October. After that, it's tough to say whether it will be prioritized. So if you need it fixed soon, I recommend trying to fix it yourself. I would try to give you some idea of where to start, but this isn't my area of expertise :cry:
This is a pretty big deal. Not being able to use docker cp
at all is pretty basic function of docker that I'm not able to use.
@jandubois should this be higher priority?
I'm also encountering this when trying to mount a file from the host into a docker container. The error message is the same as well:
flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
Hope this can be fixed soon.
I'm also encountering this when trying to mount a file from the host into a docker container. The error message is the same as well:
flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
Hope this can be fixed soon.
I don't think this is the same thing. The original issue is copying a file, not mounting. The error is different too.
@jandubois should this be higher priority?
Yes.
Does anyone know how to fix it
Any update on this?
Error: failed to copy content to container: Error response from daemon: mount /mnt/wsl/rancher-desktop/run/docker-mounts/1de3c6b5-70d4-4bf8-9371-88db2e9fcbc6:/var/lib/docker/overlay2/4a55d9547e794bca963c07fecb07d8b8789a7dc1e348981b7fc60ec37cfe9977/merged/run/docker.sock, flags: 0x5000: not a directory
I have the same error with Rancher Desktop Version: 1.12.3
Actual Behavior
Some scripts using docker are failing but works using docker desktop Maybe related to docker running inside containers, not totally sure
Steps to Reproduce
test
job with act with :act -j test
Result
Expected Behavior
Additional Information
Trying to build the repository https://github.com/rancher/cis-operator also doesn't work :
Both examples are working with Docker Desktop but are failing with Rancher Desktop
Rancher Desktop Version
1.3.0
Rancher Desktop K8s Version
1.22.7
Which container runtime are you using?
moby (docker cli)
What operating system are you using?
Windows
Operating System / Build Version
Windows 11 21H2 + WSL2 Ubuntu20.04
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