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..

Hi everybody. I use spryker on Docker Desktop (Windows 10 with WLS Ubuntu) and have a weird problem.

U02Q20KCK46
U02Q20KCK46 Posts: 12 πŸ§‘πŸ»β€πŸš€ - Cadet

Hi everybody. I use spryker on Docker Desktop (Windows 10 with WLS Ubuntu) and have a weird problem. After I restart my Windows docker/sdk start doesn't work anymore. There's a problem while starting "ssh_relay" container. Does anyone has this error, too?

ERROR: for cli_ssh_relay Cannot start service cli_ssh_relay: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "/run/desktop/mnt/host/wsl/docker-desktop-bind-mounts/Ubuntu/a38932f141186bb5275677db539fb7565450b941be00e0f823c4cf47055af32c" to rootfs at "/tmp/ssh-relay/input-ssh-auth.sock" caused: mount through procfd: 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
ERROR: Encountered errors while bringing up the project.

Comments

  • U012PCVT2DB
    U012PCVT2DB Posts: 66 πŸ§‘πŸ»β€πŸš€ - Cadet

    Hi,
    are you running the commands from windows-cmd or inside the wsl-machine?

  • U02Q20KCK46
    U02Q20KCK46 Posts: 12 πŸ§‘πŸ»β€πŸš€ - Cadet

    I am inside wsl.

  • U012PCVT2DB
    U012PCVT2DB Posts: 66 πŸ§‘πŸ»β€πŸš€ - Cadet

    and the source-files are also inside the machine?

    to be honest, i never got this error. So let's see, if we can eliminate some potential problems πŸ™‚

  • U02Q20KCK46
    U02Q20KCK46 Posts: 12 πŸ§‘πŸ»β€πŸš€ - Cadet

    Thanks for your help! Yes, all files are inside wsl. It only works for the first time. After windows restart it doesn't work anymore. When I try to start container by docker desktop itself, I got the same error.

  • U012PCVT2DB
    U012PCVT2DB Posts: 66 πŸ§‘πŸ»β€πŸš€ - Cadet

    ? do you shut them down, before restarting windows? (docker/sdk stop)

  • U02Q20KCK46
    U02Q20KCK46 Posts: 12 πŸ§‘πŸ»β€πŸš€ - Cadet

    Yes. docker/sdk stop -> restart windows -> docker/sdk start. It uses the same ubuntu-"hash". Perhaps wsl ubuntu has changed this after restart of windows?

  • U012PCVT2DB
    U012PCVT2DB Posts: 66 πŸ§‘πŸ»β€πŸš€ - Cadet

    i don't think, it creates another hash.
    So, then we should proceed to the docker-sdk and spryker-versions. and also the docker-desktop version πŸ™‚
    Are the docker-sdk and docker-desktop (nearly) latest?

  • U02Q20KCK46
    U02Q20KCK46 Posts: 12 πŸ§‘πŸ»β€πŸš€ - Cadet

    "Docker Desktop 4.4.4 (73704) is currently the newest version available."

  • U02Q20KCK46
    U02Q20KCK46 Posts: 12 πŸ§‘πŸ»β€πŸš€ - Cadet

    The only hint i found was https://giters.com/docker/for-win/issues/12406 But there's no solution 😞

  • U012PCVT2DB
    U012PCVT2DB Posts: 66 πŸ§‘πŸ»β€πŸš€ - Cadet

    Hm, that is very strange.
    Did you try using another Distro?
    I use Kali-Linux for example.

  • U012PCVT2DB
    U012PCVT2DB Posts: 66 πŸ§‘πŸ»β€πŸš€ - Cadet

    Remember, when using another distro:
    stop spryker-containers and enable the docker-integration in Docker-Desktop for the new distro

  • U02Q20KCK46
    U02Q20KCK46 Posts: 12 πŸ§‘πŸ»β€πŸš€ - Cadet

    docker/sdk reset ist working, unfortunately only till the next windows restart. weird.

  • U02Q20KCK46
    U02Q20KCK46 Posts: 12 πŸ§‘πŸ»β€πŸš€ - Cadet

    But thank you very much for your help.

  • U02Q20KCK46
    U02Q20KCK46 Posts: 12 πŸ§‘πŸ»β€πŸš€ - Cadet

    ... and time πŸ™‚

  • U012PCVT2DB
    U012PCVT2DB Posts: 66 πŸ§‘πŸ»β€πŸš€ - Cadet

    would a "normal" docker/sdk up also work? The "start" command simply restarts the containers, "up" on the other hand seems to build some containers new