THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Some useful commands to use the Docker file:
Code Block | ||
---|---|---|
| ||
## 1) Pull down the `madlib/postgres_9.6:latest` image from docker hub: docker pull madlib/postgres_9.6:latest ## 2) Launch a container corresponding to the MADlib image, mounting the source code folder to the container: docker run -d -it --name madlib -v (path to incubator-madlib directory):/incubator-madlib/ madlib/postgres_9.6 where incubator-madlib is the directory where the MADlib source code resides. ############################################## * WARNING * ################################################## # Please be aware that when mounting a volume as shown above, any changes you make in the "incubator-madlib" # folder inside the Docker container will be reflected on your local disk (and vice versa). This means that # deleting data in the mounted volume from a Docker container will delete the data from your local disk also. ############################################################################################################# ## 3) When the container is up, connect to it and build MADlib: docker exec -it madlib bash mkdir /incubator-madlib/build-docker cd /incubator-madlib/build-docker cmake .. make make doc make install ## 4) Install MADlib: src/bin/madpack -p postgres -c postgres/postgres@localhost:5432/postgres install ## 5) Several other madpack commands can now be run: # Run install check, on all modules: src/bin/madpack -p postgres -c postgres/postgres@localhost:5432/postgres install-check # Run install check, on a specific module, say svm: src/bin/madpack -p postgres -c postgres/postgres@localhost:5432/postgres install-check -t svm # Reinstall MADlib: src/bin/madpack -p postgres -c postgres/postgres@localhost:5432/postgres reinstall ## 6) Kill and remove containers (after exiting the container): docker kill madlib docker rm madlib |
...