Docker/Networking - Revision history

Admin: Replacing charlesreid1.com:3000 with git.charlesreid1.com

2019-10-09T03:22:39Z

Replacing charlesreid1.com:3000 with git.charlesreid1.com

← Older revision		Revision as of 03:22, 9 October 2019
Line 24:		Line 24:
	</pre>		</pre>

	Note this is the same as is in the d-stunnel repo on git.charlesreid1.com: https://charlesreid1.com~~:3000~~/docker/d-stunnel		Note this is the same as is in the d-stunnel repo on git.charlesreid1.com: https://git.charlesreid1.com/docker/d-stunnel

	===Binding Ports 443 and 22===		===Binding Ports 443 and 22===

Admin: /* Network Equals Host Flag */

2017-03-31T05:33:20Z

Network Equals Host Flag

← Older revision		Revision as of 05:33, 31 March 2017
Line 152:		Line 152:

	Note that you can also configure the container to share networks with the host, by adding <code>--network=host</code> when executing docker run.		Note that you can also configure the container to share networks with the host, by adding <code>--network=host</code> when executing docker run.



			=Flags=

			{{DockerFlag}}

			[[Category:Networking]]

Admin: /* Running Container */

2017-03-30T23:54:59Z

Running Container

← Older revision		Revision as of 23:54, 30 March 2017
Line 35:		Line 35:

	Now the container should be started up, and stunnel should be run from within the container:		Now the container should be started up, and stunnel should be run from within the container:

			<pre>
			docker run \
			--network=host \
			-p 443:443 -p 22:22 \
			-ti cmr_stunnel \
			/bin/bash
			</pre>

			Note: if you leave out the <code>--network=host</code> flag, and you try and listen on port 22, you will see an error:

	<pre>		<pre>
	$ ./run_docker.sh		$ ./run_docker.sh
	~~root@localhost# stunnel~~		docker: Error response from daemon: driver failed programming external connectivity on endpoint adoring_torvalds (53df66409442dab5e2a035d16238927ad004a34e410035878042a22f57af623f): Error starting userland proxy: listen tcp 0.0.0.0:22: bind: address already in use.
	...
	~~root@localhost#~~
	</pre>		</pre>

			This is because you're asking the host to dedicate port 22 to listening to the Docker container, but there is already a service (SSH) running on the host, independent of Docker, that is listening for connections.

			By specifying that the docker container should use the network host, you are avoiding the need for the host to listen on the network interface itself, and forward any traffic along to other ports. The host and container are simply utilizing the same port, on the same network interface. This allows the Docker container to communicate with the host using port 22 - the host is listening on port 22, and the docker container is forwarding traffic to port 22.

	===Checking Container Networking===		===Checking Container Networking===

Admin: /* Checking Container Networking */

2017-03-30T23:42:45Z

Checking Container Networking

@@ Line 86: / Line 86: @@
 Note that the SSH service is not run in a Docker container, it is run on the host machine.
 ==Network Equals Host Flag==
 Note that you can also configure the container to share networks with the host, by adding <code>--network=host</code> when executing docker run.

Admin: /* Checking Container Networking */

2017-03-30T23:33:55Z

Checking Container Networking

← Older revision		Revision as of 23:33, 30 March 2017
Line 84:		Line 84:
	tcp6 0 0 :::22 :::* LISTEN -		tcp6 0 0 :::22 :::* LISTEN -
	</pre>		</pre>

			Note that the SSH service is not run in a Docker container, it is run on the host machine.

	==Network Equals Host Flag==		==Network Equals Host Flag==

	Note that you can also configure the container to share networks with the host, by adding <code>--network=host</code> when executing docker run.		Note that you can also configure the container to share networks with the host, by adding <code>--network=host</code> when executing docker run.

Admin: /* Stunnel */

2017-03-30T23:31:42Z

Stunnel

@@ Line 2: / Line 2: @@
 ==Stunnel==
 Stunnel networking configuration:
@@ Line 23: / Line 25: @@
 Note this is the same as is in the d-stunnel repo on git.charlesreid1.com: https://charlesreid1.com:3000/docker/d-stunnel
 Stunnel server listens on port 443 (internal). This is mapped to port 443 (external) on the host using the <code>-p 443:443</code> flag when executing docker run.
 Stunnel forwards traffic on to 127.0.0.1 port 22. This port needs to be bound, somehow, to somewhere. Keep it simple: bind container port 22 (internal) to host port 22 (external) using <code>-p 22:22</code> when executing docker run.
 Now the container should be started up, and stunnel should be run from within the container:
@@ Line 35: / Line 41: @@
 ...
 root@localhost#
 </pre>

Admin: /* Stunnel */

2017-03-30T23:28:21Z

Stunnel

← Older revision		Revision as of 23:28, 30 March 2017
Line 27:		Line 27:

	Stunnel forwards traffic on to 127.0.0.1 port 22. This port needs to be bound, somehow, to somewhere. Keep it simple: bind container port 22 (internal) to host port 22 (external) using <code>-p 22:22</code> when executing docker run.		Stunnel forwards traffic on to 127.0.0.1 port 22. This port needs to be bound, somehow, to somewhere. Keep it simple: bind container port 22 (internal) to host port 22 (external) using <code>-p 22:22</code> when executing docker run.

			Now the container should be started up, and stunnel should be run from within the container:

			<pre>
			$ ./run_docker.sh
			root@localhost# stunnel
			...
			root@localhost#
			</pre>

	==Network Equals Host Flag==		==Network Equals Host Flag==

	Note that you can also configure the container to share networks with the host, by adding <code>--network=host</code> when executing docker run.		Note that you can also configure the container to share networks with the host, by adding <code>--network=host</code> when executing docker run.

Admin: /* Stunnel */

2017-03-30T23:26:51Z

Stunnel

@@ Line 5: / Line 5: @@
 Stunnel networking configuration:
-The stunnel server is running in a Docker container.
+The stunnel server is running in a Docker container. Here is the stunnel server configuration file:
 Stunnel server listens on port 443 (internal). This is mapped to port 443 (external) on the host using the <code>-p 443:443</code> flag when executing docker run.

Admin: Created page with "Setting up networking between containers and host. ==Stunnel== Stunnel networking configuration: The stunnel server is running in a Docker container. Stunnel server liste..."

2017-03-30T23:21:45Z

Created page with "Setting up networking between containers and host. ==Stunnel== Stunnel networking configuration: The stunnel server is running in a Docker container. Stunnel server liste..."

New page

Setting up networking between containers and host.

==Stunnel==

Stunnel networking configuration:

The stunnel server is running in a Docker container.

Stunnel server listens on port 443 (internal). This is mapped to port 443 (external) on the host using the <code>-p 443:443</code> flag when executing docker run.

Stunnel forwards traffic on to 127.0.0.1 port 22. This port needs to be bound, somehow, to somewhere. Keep it simple: bind container port 22 (internal) to host port 22 (external) using <code>-p 22:22</code> when executing docker run.

==Network Equals Host Flag==

Note that you can also configure the container to share networks with the host, by adding <code>--network=host</code> when executing docker run.