This action will force synchronization from 科学大数据开源社区/图数据库系统-gStore, which will overwrite any changes that you have made since you forked the repository, and can not be recovered!!!
Synchronous operation will process in the background and will refresh the page when finishing processing. Please be patient.
Roughly speaking, there are two ways to deploy gStore via Docker.
The first one is using Dockerfile file in the root directory of project to automatically build it. And then run the container.
Another one is downloading the mirror which has been automatically built directly, then just run it.
It's worth noting that the Docker with too high version may lead to some problems. Please read the precautions carefully. The current version of test environment is Docker CE 17.06.1
After having the correct Docker environment and network, use
git clone to download the project firstly. After inputting command
docker build -t gstore it's available to start building. In the default case, it will use the Dockerfile in the root directory. More specific explanation has been written in the Dockerfile.
After the building, using
docker run -it gstore directly to enter the container and execute other operations.
Instead of downloading project or building on your own, input
docker pull suxunbin/auto_gstore:latest to pull the mirror which has been automatically built well on the docker hub. Then input
docker run -it suxunbin/auto_gstore:latest to enter the container and execute other operations.
Owing to the uncertain influence accompanying the containerization, including but not limited to some problems about network, lock, caching, rights and so on, it's quite difficult to locate the problem when debugging. It has been known that the following problems may exist: (The host is Centos 7.4)
ENV CC="ccache g++"in the process of Dockerfile building, it will lead to compile error. The reason is still unknown and it may affect the mirror cache layer, which results in repeated errors in the later process of building.
The proportion of the loss of the performance of the container under the conditions of different file numbers/networks. The performance of running gStore in the native environment and in the container.
It's waiting for supplement.
Waiting for supplement.
The mirror of gcc:8 has conquered the space of 1.7G, bringing a lot of unnecessary things(including the environment of Go). Hoping to optimize the mirror source in the future excepting lowing the gcc's version.
There are still a large number of content waiting for supplement.
Up to now we have just given a basic version. It's only the first step of containerization.
It's the document ver1.0