Docker-compose dev site not running #32

New Issue

kawaiipunk · 2020-06-27T23:07:26Z

kawaiipunk commented

2020-06-27 23:07:26 +00:00

I follow instructions in https://git.autonomic.zone/autonomic-cooperative/autonomic.zone/src/branch/master/CONTRIBUTING.md and I get this error:

docker-compose up
ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version (e.g "2.2" or "3.3") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/

I follow instructions in https://git.autonomic.zone/autonomic-cooperative/autonomic.zone/src/branch/master/CONTRIBUTING.md and I get this error: ``` docker-compose up ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version (e.g "2.2" or "3.3") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1. For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/ ```

decentral1se commented

2020-06-28 19:21:53 +00:00

This is related to the version: "3.7" field in the docker-compose.yml file. Each version of docker-compose supports some version of the YAML schema. So, I guess you need to upgrade your docker-compose.

I am not sure how you have it currently installed? I don't know how to upgrade an already installed version. The recommended install steps are quite quick and easy though: https://docs.docker.com/compose/install/.

$ sudo curl -L "https://github.com/docker/compose/releases/download/1.26.0/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
$ sudo chmod +x /usr/local/bin/docker-compose

My version is:

➜  autonomic.zone (master) ✔ docker-compose --version
docker-compose version 1.26.0, build d4451659

This is related to the `version: "3.7"` field in the `docker-compose.yml` file. Each version of `docker-compose` supports some version of the YAML schema. So, I guess you need to upgrade your `docker-compose`. I am not sure how you have it currently installed? I don't know how to upgrade an already installed version. The recommended install steps are quite quick and easy though: https://docs.docker.com/compose/install/. ``` $ sudo curl -L "https://github.com/docker/compose/releases/download/1.26.0/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose $ sudo chmod +x /usr/local/bin/docker-compose ``` My version is: ``` ➜ autonomic.zone (master) ✔ docker-compose --version docker-compose version 1.26.0, build d4451659 ```

kawaiipunk commented

2020-06-29 14:28:28 +00:00

Well spotted!

Unfortuantly now I am getting a new error:

docker-compose up
Creating network "autonomiczone_default" with the default driver
ERROR: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network

Well spotted! Unfortuantly now I am getting a new error: ``` docker-compose up Creating network "autonomiczone_default" with the default driver ERROR: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network ```

decentral1se commented

2020-06-29 14:29:32 +00:00

Think you need a docker network prune run.

Think you need a `docker network prune` run.

kawaiipunk commented

2020-06-29 14:51:29 +00:00

Ran that and no luck I'm afraid.

I'm a bit stumped because I don't have any networks running that would clash afaik. I'm not running any other containers right now.

docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
7a6537cef7ea        bridge              bridge              local
bd42d6ef3769        host                host                local
403b4b6755d3        none                null                local

Ran that and no luck I'm afraid. I'm a bit stumped because I don't have any networks running that would clash afaik. I'm not running any other containers right now. ``` docker network ls NETWORK ID NAME DRIVER SCOPE 7a6537cef7ea bridge bridge local bd42d6ef3769 host host local 403b4b6755d3 none null local ```

kawaiipunk commented

2020-06-29 14:56:53 +00:00

Turns out this was related to a VPN I was running. Apparently that can mess with Docker networks. Lesson learned. Closing.

kawaiipunk closed this issue

2020-06-29 14:56:53 +00:00

This repo is archived. You cannot comment on issues.