openstack/anchor
Code Issues Proposed changes

Improved readme

Browse Source 
Updated description of docker deployment to include passing the
docker network to anchor so certificate requests can pass
validation.

Change-Id: Ib93e0b4806f919da1d33658f2a2ab38b81fdb4d8
This commit is contained in:
Doug Chivers 2017-02-21 09:49:30 -05:00
parent 0810685ce1
commit 0ecce126dc
1 changed files with 18 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
README.rst
View File

@ -169,13 +169,25 @@ To start the service in the container and serve Anchor on port 5016:
docker run -p 5016:5016 anchor docker run -p 5016:5016 anchor
The anchor application should be accessible on port 5016. If you are When Anchor is running in a container, certificate requests will not pass
running docker natively on Linux, that will be 5016 on localhost validation unless the docker network is added as a source_cidr in the Anchor
(127.0.0.1). If you are running docker under Microsoft Windows or Apple configuration and then passed into the container. Find the network by starting
OSX it will be running in a docker machine. To find the docker machine the container, inspecting the docker network and finding the anchor container:
IP address run:
docker-machine ip default docker run -p 5016:5016 --name=anchor anchor
docker network inspect bridge
Under the 'containers' section, find the 'anchor' container and find the
IPv4Address. For example:
"Containers": {
"6998a....5f4a57": {
"Name": "anchor",
"MacAddress": "02:42:ac:11:00:03",
"IPv4Address": "172.17.0.3/16",
Add this network as a source_cidr to the config.json, and pass it to the
docker container as described above.
Running Anchor in production Running Anchor in production
============================ ============================