-
-
Notifications
You must be signed in to change notification settings - Fork 635
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
Invalid compose file because networks structure is wrong #334
Comments
Update the docker version to 20 or use release v0.6 |
@xaabi6 @evertramos my version of docker is 20 but I got the same issue
It was resolved by checking out version 0.6 |
I finally reverted Update the network structure and everything went fine for me @allanext, but it's quite interesting to know that it's not working for you in docker version 20. |
@xaabi6 and @allanext my bad... I was in a hurry, just wanted you to fix the issue. But the message you received was from docker-compose not docker, so the version you are using of docker-compose 1. This new structure is for version 2. I will add to the home a version compatibility soon. Sorry for the hurry again! |
Thanks for the clarification @evertramos, I never thought the culprit would be the docker-compose version but it makes sense because otherwise it would have worked for @allanext. |
For anyone still having trouble, you need to install compose switch: https://docs.docker.com/compose/cli-command/#compose-switch |
@xaabi6 @evertramos I've set docker-compose 2 and I still have the network error:
with the trunk i get:
with the tag
I've also installed docker-switch as suggested by @mlysle:
|
@xaabi6 @evertramos removing |
@xaabi6 @evertramos I've just installed a fresh version and the issue is still there. Shouldn't |
@allanext what version of docker-compose do you have installed? ref. #334 (comment) |
Hi @evertramos here are the versions:
|
@allanext not sure what would cause that... I will check this when I get the time, but this network structure is external, so it must be informed in our compose, once the network may already exist, when I get a chance I will come back to this thread. |
Describe the bug
With the change introduced in commit Update the network structure, I get the following error:
To Reproduce
Steps to reproduce the behavior:
fresh-start.sh
Expected behavior
It should read it and continue without failing.
Server info:
The text was updated successfully, but these errors were encountered: