centersl/docker-docs
1
0
Fork 0
mirror of https://github.com/docker/docs.git synced 2026-03-27 14:28:47 +07:00
Code Issues Packages Projects Releases Wiki Activity

Fix broken link to dockerlinks (#2786)

Browse Source
This commit is contained in:
Misty Stanley-Jones
2017-04-14 10:30:34 -07:00
committed by GitHub
parent efcc91b893
commit f2e3d98456
5 changed files with 860 additions and 860 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
articles/basics/index.html
View File

@@ -1398,7 +1398,7 @@ $ docker pull ubuntu
</code></pre>
<p>This will find the <code>ubuntu</code> image by name on
<a href="/articles/articles/userguide/dockerrepos/#searching-for-images"><em>Docker Hub</em></a>
<a href="/userguide/dockerrepos/#searching-for-images"><em>Docker Hub</em></a>
and download it from <a href="https://hub.docker.com">Docker Hub</a> to a local
image cache.</p>
@@ -1564,7 +1564,7 @@ $ docker images
<p>You now have an image state from which you can create new instances.</p>
<p>Read more about <a href="/articles/articles/userguide/dockerrepos"><em>Share Images via
<p>Read more about <a href="/userguide/dockerrepos"><em>Share Images via
Repositories</em></a> or
continue to the complete <a href="/articles/articles/reference/commandline/cli"><em>Command
Line</em></a></p>

14
articles/index.xml
View File

@@ -1140,7 +1140,7 @@ of another container. Of course, if the host system is setup
accordingly, containers can interact with each other through their
respective network interfaces — just like they can interact with
external hosts. When you specify public ports for your containers or use
&lt;a href=&#34;http://localhost/articles/articles/userguide/dockerlinks&#34;&gt;&lt;em&gt;links&lt;/em&gt;&lt;/a&gt;
&lt;a href=&#34;http://localhost/userguide/dockerlinks&#34;&gt;&lt;em&gt;links&lt;/em&gt;&lt;/a&gt;
then IP traffic is allowed between containers. They can ping each other,
send/receive UDP packets, and establish TCP connections, but that can be
restricted if necessary. From a network architecture point of view, all
@@ -1425,7 +1425,7 @@ $ docker pull ubuntu
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This will find the &lt;code&gt;ubuntu&lt;/code&gt; image by name on
&lt;a href=&#34;http://localhost/articles/articles/userguide/dockerrepos/#searching-for-images&#34;&gt;&lt;em&gt;Docker Hub&lt;/em&gt;&lt;/a&gt;
&lt;a href=&#34;http://localhost/userguide/dockerrepos/#searching-for-images&#34;&gt;&lt;em&gt;Docker Hub&lt;/em&gt;&lt;/a&gt;
and download it from &lt;a href=&#34;https://hub.docker.com&#34;&gt;Docker Hub&lt;/a&gt; to a local
image cache.&lt;/p&gt;
@@ -1591,7 +1591,7 @@ $ docker images
&lt;p&gt;You now have an image state from which you can create new instances.&lt;/p&gt;
&lt;p&gt;Read more about &lt;a href=&#34;http://localhost/articles/articles/userguide/dockerrepos&#34;&gt;&lt;em&gt;Share Images via
&lt;p&gt;Read more about &lt;a href=&#34;http://localhost/userguide/dockerrepos&#34;&gt;&lt;em&gt;Share Images via
Repositories&lt;/em&gt;&lt;/a&gt; or
continue to the complete &lt;a href=&#34;http://localhost/articles/articles/reference/commandline/cli&#34;&gt;&lt;em&gt;Command
Line&lt;/em&gt;&lt;/a&gt;&lt;/p&gt;
@@ -1797,7 +1797,7 @@ This document discusses advanced networking configuration
and options for Docker. In most cases you won&amp;rsquo;t need this information.
If you&amp;rsquo;re looking to get started with a simpler explanation of Docker
networking and an introduction to the concept of container linking see
the &lt;a href=&#34;http://localhost/articles/articles/userguide/dockerlinks/&#34;&gt;Docker User Guide&lt;/a&gt;.&lt;/p&gt;
the &lt;a href=&#34;http://localhost/userguide/dockerlinks/&#34;&gt;Docker User Guide&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;But &lt;code&gt;docker0&lt;/code&gt; is no ordinary interface. It is a virtual &lt;em&gt;Ethernet
@@ -2139,7 +2139,7 @@ services. If the Docker daemon is running with both &lt;code&gt;--icc=false&lt;
&lt;code&gt;ACCEPT&lt;/code&gt; rules so that the new container can connect to the ports
exposed by the other container — the ports that it mentioned in the
&lt;code&gt;EXPOSE&lt;/code&gt; lines of its &lt;code&gt;Dockerfile&lt;/code&gt;. Docker has more documentation on
this subject — see the &lt;a href=&#34;http://localhost/articles/articles/userguide/dockerlinks&#34;&gt;linking Docker containers&lt;/a&gt;
this subject — see the &lt;a href=&#34;http://localhost/userguide/dockerlinks&#34;&gt;linking Docker containers&lt;/a&gt;
page for further details.&lt;/p&gt;
&lt;blockquote&gt;
@@ -2213,7 +2213,7 @@ MASQUERADE all -- 172.17.0.0/16 0.0.0.0/0
&lt;p&gt;But if you want containers to accept incoming connections, you will need
to provide special options when invoking &lt;code&gt;docker run&lt;/code&gt;. These options
are covered in more detail in the &lt;a href=&#34;http://localhost/articles/articles/userguide/dockerlinks&#34;&gt;Docker User Guide&lt;/a&gt;
are covered in more detail in the &lt;a href=&#34;http://localhost/userguide/dockerlinks&#34;&gt;Docker User Guide&lt;/a&gt;
page. There are two approaches.&lt;/p&gt;
&lt;p&gt;First, you can supply &lt;code&gt;-P&lt;/code&gt; or &lt;code&gt;--publish-all=true|false&lt;/code&gt; to &lt;code&gt;docker run&lt;/code&gt; which
@@ -2280,7 +2280,7 @@ connect to a local container exposed port through the commonly used loopback
address: this alternative is preferred for performance reason.&lt;/p&gt;
&lt;p&gt;Again, this topic is covered without all of these low-level networking
details in the &lt;a href=&#34;http://localhost/articles/articles/userguide/dockerlinks/&#34;&gt;Docker User Guide&lt;/a&gt; document if you
details in the &lt;a href=&#34;http://localhost/userguide/dockerlinks/&#34;&gt;Docker User Guide&lt;/a&gt; document if you
would like to use that as your port redirection reference instead.&lt;/p&gt;
&lt;h2 id=&#34;ipv6&#34;&gt;IPv6&lt;/h2&gt;

1688
articles/networking/index.html
View File

File diff suppressed because it is too large Load Diff

2
articles/security/index.html
View File

@@ -1401,7 +1401,7 @@ of another container. Of course, if the host system is setup
accordingly, containers can interact with each other through their
respective network interfaces — just like they can interact with
external hosts. When you specify public ports for your containers or use
<a href="/articles/articles/userguide/dockerlinks"><em>links</em></a>
<a href="/userguide/dockerlinks"><em>links</em></a>
then IP traffic is allowed between containers. They can ping each other,
send/receive UDP packets, and establish TCP connections, but that can be
restricted if necessary. From a network architecture point of view, all

12
index.xml
View File

@@ -408,7 +408,7 @@ $ docker pull ubuntu
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This will find the &lt;code&gt;ubuntu&lt;/code&gt; image by name on
&lt;a href=&#34;http://localhost/articles/articles/userguide/dockerrepos/#searching-for-images&#34;&gt;&lt;em&gt;Docker Hub&lt;/em&gt;&lt;/a&gt;
&lt;a href=&#34;http://localhost/userguide/dockerrepos/#searching-for-images&#34;&gt;&lt;em&gt;Docker Hub&lt;/em&gt;&lt;/a&gt;
and download it from &lt;a href=&#34;https://hub.docker.com&#34;&gt;Docker Hub&lt;/a&gt; to a local
image cache.&lt;/p&gt;
@@ -574,7 +574,7 @@ $ docker images
&lt;p&gt;You now have an image state from which you can create new instances.&lt;/p&gt;
&lt;p&gt;Read more about &lt;a href=&#34;http://localhost/articles/articles/userguide/dockerrepos&#34;&gt;&lt;em&gt;Share Images via
&lt;p&gt;Read more about &lt;a href=&#34;http://localhost/userguide/dockerrepos&#34;&gt;&lt;em&gt;Share Images via
Repositories&lt;/em&gt;&lt;/a&gt; or
continue to the complete &lt;a href=&#34;http://localhost/articles/articles/reference/commandline/cli&#34;&gt;&lt;em&gt;Command
Line&lt;/em&gt;&lt;/a&gt;&lt;/p&gt;
@@ -2347,7 +2347,7 @@ This document discusses advanced networking configuration
and options for Docker. In most cases you won&amp;rsquo;t need this information.
If you&amp;rsquo;re looking to get started with a simpler explanation of Docker
networking and an introduction to the concept of container linking see
the &lt;a href=&#34;http://localhost/articles/articles/userguide/dockerlinks/&#34;&gt;Docker User Guide&lt;/a&gt;.&lt;/p&gt;
the &lt;a href=&#34;http://localhost/userguide/dockerlinks/&#34;&gt;Docker User Guide&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;But &lt;code&gt;docker0&lt;/code&gt; is no ordinary interface. It is a virtual &lt;em&gt;Ethernet
@@ -2689,7 +2689,7 @@ services. If the Docker daemon is running with both &lt;code&gt;--icc=false&lt;
&lt;code&gt;ACCEPT&lt;/code&gt; rules so that the new container can connect to the ports
exposed by the other container — the ports that it mentioned in the
&lt;code&gt;EXPOSE&lt;/code&gt; lines of its &lt;code&gt;Dockerfile&lt;/code&gt;. Docker has more documentation on
this subject — see the &lt;a href=&#34;http://localhost/articles/articles/userguide/dockerlinks&#34;&gt;linking Docker containers&lt;/a&gt;
this subject — see the &lt;a href=&#34;http://localhost/userguide/dockerlinks&#34;&gt;linking Docker containers&lt;/a&gt;
page for further details.&lt;/p&gt;
&lt;blockquote&gt;
@@ -2763,7 +2763,7 @@ MASQUERADE all -- 172.17.0.0/16 0.0.0.0/0
&lt;p&gt;But if you want containers to accept incoming connections, you will need
to provide special options when invoking &lt;code&gt;docker run&lt;/code&gt;. These options
are covered in more detail in the &lt;a href=&#34;http://localhost/articles/articles/userguide/dockerlinks&#34;&gt;Docker User Guide&lt;/a&gt;
are covered in more detail in the &lt;a href=&#34;http://localhost/userguide/dockerlinks&#34;&gt;Docker User Guide&lt;/a&gt;
page. There are two approaches.&lt;/p&gt;
&lt;p&gt;First, you can supply &lt;code&gt;-P&lt;/code&gt; or &lt;code&gt;--publish-all=true|false&lt;/code&gt; to &lt;code&gt;docker run&lt;/code&gt; which
@@ -2830,7 +2830,7 @@ connect to a local container exposed port through the commonly used loopback
address: this alternative is preferred for performance reason.&lt;/p&gt;
&lt;p&gt;Again, this topic is covered without all of these low-level networking
details in the &lt;a href=&#34;http://localhost/articles/articles/userguide/dockerlinks/&#34;&gt;Docker User Guide&lt;/a&gt; document if you
details in the &lt;a href=&#34;http://localhost/userguide/dockerlinks/&#34;&gt;Docker User Guide&lt;/a&gt; document if you
would like to use that as your port redirection reference instead.&lt;/p&gt;
&lt;h2 id=&#34;ipv6&#34;&gt;IPv6&lt;/h2&gt;