Closed changchichung closed 3 years ago
Hello @changchichung this is caused because of a bug released in the Release candidate, #104 fixes the issue but will be applied only on the next RC.
In the mean time, can you use the tag 0.1.0-rc-1 for management?
docker-compose.yml
version: "3"
services:
# Signal
signal:
image: wiretrustee/signal:0.1.0-rc-1-amd64
restart: unless-stopped
volumes:
- wiretrustee-mgmt:/var/lib/wiretrustee
ports:
- 10000:10000
# # port and command for Let's Encrypt validation
# - 443:443
# command: ["--letsencrypt-domain", "<YOUR-DOMAIN>"]
# Management
management:
image: wiretrustee/management:0.1.0-rc-1-amd64
restart: unless-stopped
volumes:
- wiretrustee-mgmt:/var/lib/wiretrustee
- ./config.json:/etc/wiretrustee/config.json
ports:
- 33073:33073
# # port and command for Let's Encrypt validation
# - 443:443
# command: ["--letsencrypt-domain", "<YOUR-DOMAIN>"]
# Coturn
coturn:
image: coturn/coturn
restart: unless-stopped
domainname: stun.wiretrustee.com
volumes:
- ./turnserver.conf:/etc/turnserver.conf:ro
# - ./privkey.pem:/etc/coturn/private/privkey.pem:ro
# - ./cert.pem:/etc/coturn/certs/cert.pem:ro
network_mode: host
volumes:
wiretrustee-mgmt:
wiretrustee-signal:
docker-compose up
2021-09-02 08:19:11 [changch@hqdc034 infrastructure_files]$ docker-compose up -d
Pulling signal (wiretrustee/signal:0.1.0-rc-1-amd64)...
0.1.0-rc-1-amd64: Pulling from wiretrustee/signal
Digest: sha256:fbdfa8a6fd64d7e108130eb0a894f0307ae6d835d4edf70db029f206bcd007a6
Status: Downloaded newer image for wiretrustee/signal:0.1.0-rc-1-amd64
Pulling management (wiretrustee/management:0.1.0-rc-1-amd64)...
0.1.0-rc-1-amd64: Pulling from wiretrustee/management
5f8c69dfd0d4: Pull complete
058300e50e8e: Pull complete
f39f4b92c7d9: Pull complete
Digest: sha256:762dcac4be80d1efad7fa48be04656d3e3e7b3b8b95df8ceb43c5012a74e7f8a
Status: Downloaded newer image for wiretrustee/management:0.1.0-rc-1-amd64
Recreating infrastructure_files_signal_1 ... done
Recreating infrastructure_files_coturn_1 ... done
Creating infrastructure_files_management_1 ... done
but the management container is not in healthy state
0f2fb827e798 coturn/coturn "docker-entrypoint.s…" 2 minutes ago Up 2 minutes infrastructure_files_coturn_1
320ebdc5d297 wiretrustee/signal:0.1.0-rc-1-amd64 "/go/bin/wiretrustee…" 2 minutes ago Up 2 minutes 0.0.0.0:10000->10000/tcp, :::10000->10000/tcp infrastructure_files_signal_1
a40a95f1dde1 wiretrustee/management:0.1.0-rc-1-amd64 "/go/bin/wiretrustee…" 2 minutes ago Restarting (1) 46 seconds ago infrastructure_files_management_1
and docker logs shows missing something
2021-09-02 08:22:05 [changch@hqdc034 infrastructure_files]$ docker logs -f infrastructure_files_management_1
time="2021-09-02T00:19:30Z" level=fatal msg="failed reading provided config file: /etc/wiretrustee/management.json: open /etc/wiretrustee/management.json: no such file or directory"
time="2021-09-02T00:19:31Z" level=fatal msg="failed reading provided config file: /etc/wiretrustee/management.json: open /etc/wiretrustee/management.json: no such file or directory"
time="2021-09-02T00:19:32Z" level=fatal msg="failed reading provided config file: /etc/wiretrustee/management.json: open /etc/wiretrustee/management.json: no such file or directory"
time="2021-09-02T00:19:32Z" level=fatal msg="failed reading provided config file: /etc/wiretrustee/management.json: open /etc/wiretrustee/management.json: no such file or directory"
time="2021-09-02T00:19:34Z" level=fatal msg="failed reading provided config file: /etc/wiretrustee/management.json: open /etc/wiretrustee/management.json: no such file or directory"
time="2021-09-02T00:19:36Z" level=fatal msg="failed reading provided config file: /etc/wiretrustee/management.json: open /etc/wiretrustee/management.json: no such file or directory"
time="2021-09-02T00:19:40Z" level=fatal msg="failed reading provided config file: /etc/wiretrustee/management.json: open /etc/wiretrustee/management.json: no such file or directory"
time="2021-09-02T00:19:47Z" level=fatal msg="failed reading provided config file: /etc/wiretrustee/management.json: open /etc/wiretrustee/management.json: no such file or directory"
time="2021-09-02T00:20:00Z" level=fatal msg="failed reading provided config file: /etc/wiretrustee/management.json: open /etc/wiretrustee/management.json: no such file or directory"
time="2021-09-02T00:20:26Z" level=fatal msg="failed reading provided config file: /etc/wiretrustee/management.json: open /etc/wiretrustee/management.json: no such file or directory"
time="2021-09-02T00:21:18Z" level=fatal msg="failed reading provided config file: /etc/wiretrustee/management.json: open /etc/wiretrustee/management.json: no such file or directory"
time="2021-09-02T00:22:19Z" level=fatal msg="failed reading provided config file: /etc/wiretrustee/management.json: open /etc/wiretrustee/management.json: no such file or directory"
2021-09-02 08:22:29 [changch@hqdc034 infrastructure_files]$
hey, @changchichung Thank you for your interest in the project! There was a bug in the location of the management service config. You can use a fixed docker-compose
However, you won't be able to fully run the API due to the missing frontend. We are finishing it and it will be open soon.
If you would like to just try the system, please proceed to https://beta.wiretrustee.com/ This is the quickest way to evaluate the system. I will let you know once the complete Getting Started guide has been published
@braginini thanks for the info . I register in https://beta.wiretrustee.com/ and bring up 2 nodes in wireguard vpn . The operation is very simple, hope to see the frontend release sooner.
barely change in docker-compose and turnserver.conf
just clone the repo and run docker-compose but return errors
any suggestions ??