KubeFATE
KubeFATE copied to clipboard
How to Deploy a Three-Party Fate Environment
**What deployment mode you are use? **
- docker-compose;
- Kuberentes.
**What KubeFATE and FATE version you are using? **
MUST Please state the KubeFATE and FATE version you found the issue
**What OS you are using for docker-compse or Kubernetes? Please also clear the version of OS. **
- OS: [e.g. iOS]
- Version [e.g. 22]
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]
To Reproduce
Clear how to reproduce your problem.
What happen?
Clear the unexpected response.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Hi, could you please elaborate where do you meet trouble for deploying a 3-party federation?
Hi, could you please elaborate where do you meet trouble for deploying a 3-party federation?
First, in parties.conf file, I change the ip list, adding one more ip address and the corresponding party id.
However, when I run the deploy.sh code in the server machine, it occurs the following error.
https://stackoverflow.com/questions/50265014/docker-compose-mounting-volume-error-no-such-file-or-directory
Are you on Windows?
WRT your original question, you can check how others deploy 3-party federation. https://github.com/FederatedAI/KubeFATE/issues/752#issuecomment-1242948392
BTW, have you ever deployed a 2-party federation successfully?
https://stackoverflow.com/questions/50265014/docker-compose-mounting-volume-error-no-such-file-or-directory
Are you on Windows?
WRT your original question, you can check how others deploy 3-party federation. #752 (comment)
BTW, have you ever deployed a 2-party federation successfully?
I am on centos, and I have successfully deployed 2-party federation on other old fate version. But now I try to deploy the newest fate v1.9.0 in three machines, and meet the error.
Try to clean up everything on your machine
cd /data/projects/fate/
cd confs-9999
docker-compose down
cd ../serving-9999
docker-copose down
docker volume rm $(docker volume ls -q | grep 9999) && docker network rm confs-9999_fate-network
Do above steps for all your party IDs, here 9999 is just an example.
The retry install 3 parties.