p4u1/docker-cli
0
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Now using the nginx docker image instead of the apache one. dotcloud/docker/issues/6374

Browse Source 
Docker-DCO-1.1-Signed-off-by: Julien Bordellier <me@julienbordellier.com> (github: jstoja)
Upstream-commit: 207d7807af35a3f1ee98e6401bff83146d2450f8
Component: engine
This commit is contained in:
Julien Bordellier
2014-06-13 09:24:09 +08:00
parent 455e8c968c
commit da74dc358a
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
components/engine/docs/sources/installation/mac.md
View File

@ -74,9 +74,9 @@ access to the container's ports.
If you run a container with an exposed port,
$ docker run --rm -i -t -p 80:80 apache
$ docker run --rm -i -t -p 80:80 nginx
then you should be able to access that Apache server using the IP address reported by:
then you should be able to access that Nginx server using the IP address reported by:
$ boot2docker ssh ip addr show dev eth1

4
components/engine/docs/sources/installation/windows.md
View File

@ -72,9 +72,9 @@ The latest version of `boot2docker` sets up a host only network adaptor which pr
If you run a container with an exposed port:
docker run --rm -i -t -p 80:80 apache
docker run --rm -i -t -p 80:80 nginx
Then you should be able to access that Apache server using the IP address reported
Then you should be able to access that nginx server using the IP address reported
to you using:
boot2docker ip