3 navsection: installguide
4 title: Installing with Docker
7 {% include 'alert_docker' %}
11 # A GNU/Linux (virtual) machine
12 # A working Docker installation
14 h2. Download the source tree
17 <pre><code>~$ <span class="userinput">cd $HOME</span> # (or wherever you want to install)
18 ~$ <span class="userinput">git clone https://github.com/curoverse/arvados.git</span>
19 </code></pre></notextile>
21 See also: "Downloading the source code":https://arvados.org/projects/arvados/wiki/Download on the Arvados wiki.
23 h2. Building the Arvados Docker containers
25 First we need a suitable @config.yml@ file.
28 <pre><code>~$ <span class="userinput">cd arvados/docker</span>
29 ~$ <span class="userinput">cp config.yml.example config.yml</span>
30 </code></pre></notextile>
32 Now it's time to edit the @config.yml@ file and fill in suitable values for at a minimum these parameters:
40 h2. Running the Arvados Docker containers
42 The @arvdock@ command can be used to start and stop the docker containers. It has a number of options:
45 <pre><code>~$ <span class="userinput">cd arvados/docker</span>
46 ~$ <span class="userinput">./arvdock -h</span>
48 usage: ./arvdock (start|stop|restart|test) [options]
50 ./arvdock start/stop/restart options:
51 -d [port], --doc[=port] Documentation server (default port 9898)
52 -w [port], --workbench[=port] Workbench server (default port 9899)
53 -s [port], --sso[=port] SSO server (default port 9901)
54 -a [port], --api[=port] API server (default port 9900)
55 -k, --keep Keep servers
56 --ssh Enable SSH access to server containers
57 -h, --help Display this help and exit
59 If no options are given, the action is applied to all servers.
61 ./arvdock test [testname] [testname] ...
62 By default, all tests are run.
67 The @--ssh@ option can be useful to debug issues with the Docker containers; it allows you to ssh into the running containers as the @root@ user, provided you have access to the private key that matches the public key specified in @config.yml@'s PUBLIC_KEY_PATH variable.
69 Start the docker containers:
72 <pre><code>~$ <span class="userinput">cd arvados/docker</span>
73 ~$ <span class="userinput">./arvdock start</span>
76 /usr/bin/docker.io run -d -i -t -p 9901:443 --name sso_server arvados/sso
79 /usr/bin/docker.io run -d -i -t -p 9900:443 --name api_server --link sso_server:sso arvados/api
82 /usr/bin/docker.io run -d -i -t -p 25107:25107 --name keep_server_0 -v /tmp/tmp.aCSx8Pq6Wb:/dev/keep-0 --link api_server:api arvados/keep
85 /usr/bin/docker.io run -d -i -t -p 25108:25107 --name keep_server_1 -v /tmp/tmp.m4OQ9WB73G:/dev/keep-0 --link api_server:api arvados/keep
88 /usr/bin/docker.io run -d -i -t -p 9898:80 --name doc_server arvados/doc
90 *****************************************************************
91 You can access the Arvados documentation at http://localhost:9898
92 *****************************************************************
96 /usr/bin/docker.io run -d -i -t -p 9899:80 --name workbench_server --link api_server:api arvados/workbench
98 *****************************************************************
99 You can access the Arvados workbench at http://localhost:9899
100 *****************************************************************
101 </code></pre></notextile>
103 h2. Accessing workbench
105 Point your browser to the Dockerized workbench:
108 <pre><code><span class="userinput">https://localhost:9899</span>
112 Now use the google account you specified as @API_AUTO_ADMIN_USER@ in @config.yml@ to log in. You will be prompted *twice* by your browser that you are accessing a site with an untrusted SSL certificate. This is normal; by default the Arvados Docker installation uses self-signed SSL certificates for the SSO and API servers, respectively.