Calling Developers!
We are reenergizing our code contribution process! Learn More

What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

On Win10 I've tried exporting the wsl to a different drive and then importing it, but now i can't se

Options
U04RMV59JP8
U04RMV59JP8 Posts: 23 🧑🏻‍🚀 - Cadet
edited May 2023 in Help

On Win10 I've tried exporting the wsl to a different drive and then importing it, but now i can't seem to start it. It always fails at this moment:
[+] Running 3/4
⠿ Network oneal_b2c_dev_public Created 0.0s
⠿ Network oneal_b2c_dev_private Created 0.0s
⠿ Container oneal_b2c_dev_cli_ssh_relay_1 Starting 0.9s
⠿ Container oneal_b2c_dev_cli_1 Started 0.9s
Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/37058a6d37f441bd74afb99b97f250f2a1c3f4a0ca903216c2c4f2ae8795e879" to rootfs at "/tmp/ssh-relay/input-ssh-auth.sock": mount /run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/37058a6d37f441bd74afb99b97f250f2a1c3f4a0ca903216c2c4f2ae8795e879:/tmp/ssh-relay/input-ssh-auth.sock (via /proc/self/fd/14), 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
Creating a new instance of ubuntu now fails as well on the same step
[+] Running 3/4
⠿ Network oneal_b2c_dev_private Created 0.0s
⠿ Network oneal_b2c_dev_public Created 0.0s
⠿ Container oneal_b2c_dev_cli_ssh_relay_1 Starting 1.0s
⠿ Container oneal_b2c_dev_cli_1 Started 1.0s
Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu-20.04/e2148961c7550c04da46c87a1d11b6f752a71bf5861053fe4d47b724a7ca4330" to rootfs at "/tmp/ssh-relay/input-ssh-auth.sock": mount /run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu-20.04/e2148961c7550c04da46c87a1d11b6f752a71bf5861053fe4d47b724a7ca4330:/tmp/ssh-relay/input-ssh-auth.sock (via /proc/self/fd/14), 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
I can still seem to be able to start spryker via docker/sdk start, and the services get up with the exception of dev_cli_ssh_relay_1.

Comments

  • U012PCVT2DB
    U012PCVT2DB Posts: 66 🧑🏻‍🚀 - Cadet
    Options

    maybe you have to throw away EVERY docker-container + -volume and re-setup spryker?

    I have an exported WSL-machine on a different drive, but have never tried "setup spryker -> move WSL machine -> start spryker"

    but i am with you, i would have not assumed, that it would matter to docker 😮

  • U04RMV59JP8
    U04RMV59JP8 Posts: 23 🧑🏻‍🚀 - Cadet
    Options

    Okay, so deleting all containers and volumes, alongside deleting docker/deployment/default fixed this.
    The latter was probably not needed to be done, but i've gone full reset to make sure i don't have to fix another kind of problem