forked from cybercongress/go-cyber
-
Notifications
You must be signed in to change notification settings - Fork 3
/
docker-compose.yml
69 lines (63 loc) · 1.29 KB
/
docker-compose.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
version: '3'
services:
cybernode0:
container_name: cybernode0
image: "cybercongress/cyber"
ports:
- "26656-26657:26656-26657"
- "1317:1317"
environment:
- ID=0
- LOG=${LOG:-cyber.log}
volumes:
- ./build:/cyber:Z
networks:
localnet:
ipv4_address: 192.168.10.2
cybernode1:
container_name: cybernode1
image: "cybercongress/cyber"
ports:
- "26659-26660:26656-26657"
environment:
- ID=1
- LOG=${LOG:-cyber.log}
volumes:
- ./build:/cyber:Z
networks:
localnet:
ipv4_address: 192.168.10.3
cybernode2:
container_name: cybernode2
image: "cybercongress/cyber"
environment:
- ID=2
- LOG=${LOG:-cyber.log}
ports:
- "26661-26662:26656-26657"
volumes:
- ./build:/cyber:Z
networks:
localnet:
ipv4_address: 192.168.10.4
cybernode3:
container_name: cybernode3
image: "cybercongress/cyber"
environment:
- ID=3
- LOG=${LOG:-cyber.log}
ports:
- "26663-26664:26656-26657"
volumes:
- ./build:/cyber:Z
networks:
localnet:
ipv4_address: 192.168.10.5
networks:
localnet:
driver: bridge
ipam:
driver: default
config:
-
subnet: 192.168.10.0/16