FATE stand-alone deployment
Encountered a variety of tricks, the head is big
Installed the centos7 system in the virtual machine according to the tutorial in the previous blog , and it is relatively smooth
Next installed python3 , because the version that comes with the system is python2.7
pip cannot be used
After installing python3.6 for the first time , I found that the pip command could not be used . It turned out that there was a problem when establishing the soft connection.
You can refer to https://blog.csdn.net/u010510962/article/details/80690084
After installing python3, install jdk, Redis, and mysql.
After that, it officially started according to the tutorial given by GitHub
Install docker first , without checking the version of docker installed, and then install docker-compose
After the installation is successful, when deploying
First, download the deployment version of the official website
wget https://webank-ai-1251170195.cos.ap-guangzhou.myqcloud.com/docker_standalone-fate-1.2.0.tar.gz
and unzip
tar -xvf docker_standalone-fate-1.2.0.tar.gz
Then start executing the deployment script
cd docker_standalone-fate-1.2.0
bash install_standalone_docker.sh
At this step, something went wrong! ! !
The container is not up
After the execution, there is no error, but docker ps can see that only one container is started
So docker ps -a looks at the id that did not start
Then use docker start container id to start
The startup is successful, use docker ps to check again, and find that the container that was just started is not displayed.
But it was clearly launched successfully! So docker ps -a to see what is going on
It was found that the container was indeed started successfully, but it hung up again! ! !
Since then, a long process of searching for problems has begun, and the thinking is not right.
I found the Docker container on the Internet and automatically shut down after starting it. There are many problems and I don't understand it. Later, I asked the big guy to ask. If the big guy said that the container is empty, it will exit.
Start checking various environments
(1) Check python3
When I execute python, I find that the version is python2.7, do not have this command when executing python3? ? ?
Python is messed up, reinstall python3, and then change the system python to python3
It is estimated that it is the problem of python, try to execute the deployment script again, or that problem
(2) Checked the version of docker before it was 12, and the tutorial said that it is more than 18,
Update docker
Reference https://blog.csdn.net/qq_39629343/article/details/80168084
docker -v updated to 19
Try to execute the deployment script again, still the problem
(3) Later, I forgot how to mess around, (maybe I want to delete the original docker-compose and reinstall one). As a result, a new problem appeared (it seems that I accidentally deleted that file)
-bash: /usr/local/bin/docker-compose: Permission denied
Check again docker-compose,
There is no problem to execute docker-compose, the installation is successful
Only go to the official website https://github.com/docker/compose/releases/tag/1.14.0-rc2
Go down and rename it to docker-compose and put it in the / usr / local / bin / path, then add the permissions
chmod +x /usr/local/bin/docker-compose
(4) The above problem is solved, but the initial problem is still
So use pip to install docker-compose again
pip install docker-compose
No error or successful installation
Try another command and it shows that the installation was successful
pip install -U docker-compose==1.23.2
After installation, delete the original file docker_standalone-fate-1.2.0
Re-decompression, so it is recommended not to delete the installation package immediately after decompression, otherwise it will have to be re-run again, which is too wasteful
Run the deployment script again
bash install_standalone_docker.sh
docker ps
Hahaha succeeded, both containers got up
If you find that both are not up, you can use docker start to start both of them separately.
Follow the tutorial on GitHub to be fine
