autonomic-cooperative/autonomic.zone
Archived
4
0
Fork 0
Code Issues 15 Pull Requests 2 Releases Activity

Docker-compose dev site not running #32

New Issue
Closed
opened 2020-06-27 23:07:26 +00:00 by kawaiipunk · 5 comments
kawaiipunk commented 2020-06-27 23:07:26 +00:00
Owner
Copy Link
Copy Source

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
Contributor
Copy Link
Copy Source

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
Author
Owner
Copy Link
Copy Source

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
Contributor
Copy Link
Copy Source

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
Author
Owner
Copy Link
Copy Source

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
Author
Owner
Copy Link
Copy Source

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

Turns out this was related to a VPN I was running. Apparently that can mess with Docker networks. Lesson learned. Closing.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
aadil (Aadil Ayub) analuisa autono-bot (Autono-bot) autonomic cas (Cassowary Rusnov) kawaiipunk (KawaiiPunk) knoflook lucas maazah notplants renovate-bot (Renovate Bot) tma trav (Trav Fryer) veganvenom
No Assignees
2 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: autonomic-cooperative/autonomic.zone#32