You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 1, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+3-26Lines changed: 3 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,9 @@ This project is meant to replace the traditional Vagrant VM "devstack" with a mu
6
6
7
7
## Getting Started
8
8
9
-
All of the services can be run by following the steps below.
9
+
All of the services can be run by following the steps below. Note that since we are running many containers, you should
10
+
configure Docker with a sufficient amount of resources. Our testing found that [configuring Docker for Mac](https://docs.docker.com/docker-for-mac/#/advanced)
11
+
with 2 CPUs and 4GB of memory works well.
10
12
11
13
1. The Docker Compose file mounts a host volume for each service's executing code. The host directory is expected to be
12
14
a sibling of this directory. For example, if this repo is cloned to `~/workspace/devstack`, host volumes will be
@@ -38,28 +40,3 @@ After the services have started, if you need shell access to one of the services
38
40
```
39
41
$ make devstack.open.discovery
40
42
```
41
-
42
-
## Loopback Alias
43
-
44
-
Containers making requests to the LMS and Studio must communicate with ports exposed on the host system by the Vagrant VM. (This assumes that the LMS and Studio are still running in the traditional Vagrant-based devstack.)
45
-
46
-
This is fine on Linux, but doesn't work out of the box on OS X. Attempting to access localhost on a container will result
47
-
in talking to the Docker for Mac HyperKit VM, not the host machine.
48
-
49
-
While it's true that you can get this to work by accessing your Mac's external IP from your containers, this isn't ideal because
50
-
it won't work if you have no network access on your host. Your external IP also changes as you switch networks, meaning you'd have
51
-
to change the IP accessed by your containers every time you changed networks.
52
-
53
-
A better solution, borrowed from the [Docker forums](https://forums.docker.com/t/access-host-not-vm-from-inside-container/11747/10),
54
-
is to give your host a fixed address by creating a [loopback](http://askubuntu.com/questions/247625/what-is-the-loopback-device-and-how-do-i-use-it)
55
-
alias. This is done for you by the `devstack.start` target.
56
-
57
-
The result is a fixed IP which your containers can use to access ports on your host machine. Note that the underlying script uses `sudo`;
58
-
adding IP addresses requires root access. Also note that the alias will not survive a host reboot, which is why the `devstack.start` target
59
-
always attempts to set up the loopback for you.
60
-
61
-
Part of the loopback alias setup includes adding a line to the `/etc/hosts` file on your machine. If you want to stop using devstack, you can clean this up by opening your `/etc/hosts` file and removing this line:
0 commit comments