Browse code

Fixes the README build example to make it work

Jonas Pfenniger authored on 2013/05/12 07:50:06
Showing 1 changed files
... ...
@@ -77,14 +77,14 @@ commands, the *order* in which the commands are executed expresses *dependencies
77 77
 Here's a typical docker build process:
78 78
 
79 79
 ```bash
80
-from	ubuntu:12.10
81
-run	apt-get update
82
-run	apt-get install python
83
-run	apt-get install python-pip
84
-run	pip install django
85
-run	apt-get install curl
86
-run	curl http://github.com/shykes/helloflask/helloflask/master.tar.gz | tar -zxv
87
-run	cd master && pip install -r requirements.txt
80
+from ubuntu:12.10
81
+run apt-get update
82
+run DEBIAN_FRONTEND=noninteractive apt-get install -q -y python
83
+run DEBIAN_FRONTEND=noninteractive apt-get install -q -y python-pip
84
+run pip install django
85
+run DEBIAN_FRONTEND=noninteractive apt-get install -q -y curl
86
+run curl -L https://github.com/shykes/helloflask/archive/master.tar.gz | tar -xzv
87
+run cd helloflask-master && pip install -r requirements.txt
88 88
 ```
89 89
 
90 90
 Note that Docker doesn't care *how* dependencies are built - as long as they can be built by running a unix command in a container.