-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: failed to start containers: samba #7
Comments
Hi @peter197321, I looked into this a bit today. It seems that when using either Hyper-V or the WSL 2 version of Docker for Windows, it tries to directly listen on the same adapter as the host.(Previous versions evidently bridged instead) This is most likely what is causing the error, because Windows always grabs port 445 for the built-in file sharing. My guess is that Virtual Box in Docker Toolbox wouldn't have this issue, but that's not an idea solution if you are able to run using Hyper-V or WSL 2. I'm honestly not sure of the solution. I don't believe Windows Explorer will allow for specifying a different port, which would be the easiest thing. There may indeed be another way to address the issue, but I'm currently unaware of one. |
Hello again @peter197321, I did a bit more research, and if you are using WSL2 it seems there is no longer a need for the volume or for the samba container. While it will require some understanding of WSL2, I'll try to give an example. Ideally this will be added to the docs at some point. Use explorer.exe to show files within the root filesystem inside WSL2
Now you should something like the following screenshot: Setup and use YoctoNote this is just an example, but should show the general flow.
DisclaimerHopefully this is helpful. However, there may be issues with storage space/reclamation on WSL2 based on the comments here. With some investigation, my guess is you will be able to sort them out. There may even be other issues I'm unaware of considering that I used WSL2 for the first time in order to write this post. |
I had a similar issue on macOS and my solution was to map to a different host port (446) And then connect to smb://localhost:446 Hopefully this works for you as well |
I'm trying to create samba container on my windows10 host machine and running the command
it gives me an error:
can you please point me where should I look at to solve this?
The text was updated successfully, but these errors were encountered: