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.
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
-
Hi,
are you running the commands from windows-cmd or inside the wsl-machine?0 -
I am inside wsl.
0 -
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 π
0 -
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.
0 -
? do you shut them down, before restarting windows? (docker/sdk stop)
0 -
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?
0 -
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?0 -
"Docker Desktop 4.4.4 (73704) is currently the newest version available."
0 -
The only hint i found was https://giters.com/docker/for-win/issues/12406 But there's no solution π
0 -
Hm, that is very strange.
Did you try using another Distro?
I use Kali-Linux for example.0 -
Remember, when using another distro:
stop spryker-containers and enable the docker-integration in Docker-Desktop for the new distro0 -
docker/sdk reset ist working, unfortunately only till the next windows restart. weird.
0 -
But thank you very much for your help.
0 -
... and time π
0 -
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
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 84 Spryker News
- 977 Developer Corner
- 828 Spryker Development
- 91 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 36 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 32 Job Opportunities
- 3.2K π Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 33 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random