Skip to content
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

Setup error - Windows 10 with WSL2 #163

Open
xdosil opened this issue Apr 13, 2022 · 7 comments
Open

Setup error - Windows 10 with WSL2 #163

xdosil opened this issue Apr 13, 2022 · 7 comments

Comments

@xdosil
Copy link

xdosil commented Apr 13, 2022

When I start the setup option, always show the same message and the containers couldn't been created:
Error response from daemon: Invalid network mode: invalid container format container:<name|id>

Did anyone know to solve?
Thanks!

@JeroenBoersma
Copy link
Owner

It looks like a problem in WSL2, IIRC the commands you run in WSL are send to the host(Windows Docker Service)

You could take a look at the https://github.com/JeroenBoersma/docker-compose-development/tree/development-docker-compose-2 branch, I do not have a WSL laying around ATM to test this.

It could be that WSL2 + docker is advanced enough to run the latest branch.
Bigest change in that branch is the networking part.

Let me know if anything chages

@xdosil
Copy link
Author

xdosil commented Apr 14, 2022

Thanks for your quick response, but, Didn't work for me. The same problem persist. :(

@esjdev
Copy link

esjdev commented Apr 14, 2022

Thanks for your quick response, but, Didn't work for me. The same problem persist. :(

Before installing using the branch he indicated, did you remove all containers, images and volumes? if not, do so, and then re-install everything from scratch with the branch he indicated.

@xdosil
Copy link
Author

xdosil commented Apr 14, 2022

Hi @esjdev,

Thanks for your response.

How you tell, before install I removed all the volumes and images. I will try again, to be sure and I will tell you anything.

Thanks!

@xdosil
Copy link
Author

xdosil commented Apr 14, 2022

Nop. Always the same error....
imagen

@JeroenBoersma
Copy link
Owner

As mentioned here and totally overlookied... I fixed a bug related to MySQL.. .maybe it is related to this...
Maybe this also solves your error. Maybe this is something else, but then I should have more information :)

#165 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@JeroenBoersma @xdosil @esjdev and others