paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-02 13:03:29 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Add a section about enabling docker before doing vagrant up.

Browse Source 
Many Linux distros like Debian Buster, Fedora 29, etc. have a policy
where any services installed are disabled by default. So we should let
the developer know that they should explicitly enable and start the
Docker daemon.

Also, we should be verbose on how to do vagrant up using Docker as a
provider specifically (and similar for Virtualbox).
This commit is contained in:
Hemanth V. Alluri
2019-07-15 23:46:26 +05:30
committed by Tim Abbott
parent f97bb6b65c
commit cb21207a4b
1 changed files with 33 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

41
docs/development/setup-vagrant.md
View File

@@ -121,6 +121,28 @@ $ groups | grep docker
christie adm cdrom sudo dip plugdev lpadmin sambashare docker
```
##### 3. Make sure the Docker daemon is running:
On some versions of Ubuntu, newly installed services like Docker are
not automatically enabled and started after installation. You can
check using the following:
```
$ systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2019-07-15 23:20:46 IST; 18min ago
```
If the service is not running, you'll see `Active: inactive (dead)` on
the second line, and will need to enable and start the Docker service
using the following:
```
sudo systemctl enable docker
sudo systemctl start docker
```
Now you are ready for [Step 2: Get Zulip Code.](#step-2-get-zulip-code)
#### Debian
@@ -247,14 +269,16 @@ environment.](#step-3-start-the-development-environment)
### Step 3: Start the development environment
Change into the zulip directory and tell vagrant to start the Zulip
development environment with `vagrant up`.
development environment with `vagrant up`:
```
christie@win10 ~
$ cd zulip
# On Windows or macOS:
cd zulip
vagrant up --provider=virtualbox
christie@win10 ~/zulip
$ vagrant up
# On Linux:
cd zulip
vagrant up --provider=docker
```
The first time you run this command it will take some time because vagrant
@@ -484,9 +508,10 @@ Check out the Vagrant documentation to learn more about
#### Resuming the development environment
When you're ready to work on Zulip again, run `vagrant up`. You will also need
to connect to the virtual machine with `vagrant ssh` and re-start the Zulip
server:
When you're ready to work on Zulip again, run `vagrant up` (no need to
pass the `--provider` option required above). You will also need to
connect to the virtual machine with `vagrant ssh` and re-start the
Zulip server:
```
christie@win10 ~/zulip