Docker - Revision history

Admin at 09:40, 28 February 2018

2018-02-28T09:40:16Z

← Older revision		Revision as of 09:40, 28 February 2018
Line 2:		Line 2:

	It's like [[Homebrew]] or [[Aptitude]] for apps.		It's like [[Homebrew]] or [[Aptitude]] for apps.

			[[Docker/Troubleshooting]]

	[[Docker/Network Debugging]]		[[Docker/Network Debugging]]

Admin at 18:53, 23 September 2017

2017-09-23T18:53:56Z

← Older revision		Revision as of 18:53, 23 September 2017
Line 4:		Line 4:

	[[Docker/Network Debugging]]		[[Docker/Network Debugging]]

	~~=Flags=~~

	~~{{DockerFlag}}~~

	=References=		=References=
Line 20:		Line 16:

	Potential security issues with Docker containers: https://blog.docker.com/2013/08/containers-docker-how-secure-are-they/		Potential security issues with Docker containers: https://blog.docker.com/2013/08/containers-docker-how-secure-are-they/

			=Flags=

			{{DockerFlag}}

Admin at 10:40, 16 August 2017

2017-08-16T10:40:30Z

← Older revision		Revision as of 10:40, 16 August 2017
Line 4:		Line 4:

	[[Docker/Network Debugging]]		[[Docker/Network Debugging]]

			=Flags=

			{{DockerFlag}}

	=References=		=References=
Line 9:		Line 13:
	Docker's documentation is excellent: https://docs.docker.com/		Docker's documentation is excellent: https://docs.docker.com/

	Docker command line: https://docs.docker.com/engine/reference/commandline/cli/~~#environment-variables~~		Docker from the command line: https://docs.docker.com/engine/reference/commandline/cli/

	~~Docker run: https://docs.docker.com/engine/reference/commandline/run/#full-container-capabilities---privileged~~

	Docker to run memcached (Digital Ocean guide): https://www.digitalocean.com/community/tutorials/docker-explained-how-to-create-docker-containers-running-memcached		Docker to run memcached (Digital Ocean guide): https://www.digitalocean.com/community/tutorials/docker-explained-how-to-create-docker-containers-running-memcached

	Note that many Docker issues on Github contain a wealth of useful debugging strategies and commands for checking the state of networks, ports, etc.: https://github.com/docker/docker/issues/13914		Note that many Docker issues on Github contain a wealth of useful debugging strategies and commands for checking the state of networks, ports, etc. Example: https://github.com/docker/docker/issues/13914

	~~How secure are docker containers, really? https://blog.docker.com/2013/08/containers-docker-how-secure-are-they/~~



	~~{{DockerFlag}}~~		Potential security issues with Docker containers: https://blog.docker.com/2013/08/containers-docker-how-secure-are-they/

Admin: /* april 19 debugging */

2017-05-07T08:14:12Z

april 19 debugging

@@ Line 3: / Line 3: @@
 It's like [[Homebrew]] or [[Aptitude]] for apps.
-=april 19 debugging=
+[[Docker/Network Debugging]]
 =References=

Admin: /* april 19 debugging */

2017-04-19T23:03:31Z

april 19 debugging

← Older revision		Revision as of 23:03, 19 April 2017
Line 30:		Line 30:

	Yes, of course, two minutes later everything just MAGICALLY works somehow, after the fifth time trying the EXACT SAME SET OF COMMANDS.		Yes, of course, two minutes later everything just MAGICALLY works somehow, after the fifth time trying the EXACT SAME SET OF COMMANDS.

			Nmap was not helping: port 9990 was open, but was not showing up in any nmap scans. See:

			<pre>
			$ nmap reidmachine.party

			Starting Nmap 6.47 ( http://nmap.org ) at 2017-04-19 23:02 UTC
			Nmap scan report for reidmachine.party (96.126.102.36)
			Host is up (0.00082s latency).
			rDNS record for 96.126.102.36: li335-36.members.linode.com
			Not shown: 998 closed ports
			PORT STATE SERVICE
			22/tcp open ssh
			8081/tcp open blackice-icecap

			Nmap done: 1 IP address (1 host up) scanned in 0.08 seconds
			</pre>

			but when port 9990 is specified, it discovers it:

			<pre>
			$ nmap -p 9990 reidmachine.party

			Starting Nmap 6.47 ( http://nmap.org ) at 2017-04-19 23:03 UTC
			Nmap scan report for reidmachine.party (96.126.102.36)
			Host is up (0.00046s latency).
			rDNS record for 96.126.102.36: li335-36.members.linode.com
			PORT STATE SERVICE
			9990/tcp open osm-appsrvr

			Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds
			</pre>

	=References=		=References=

Admin: /* april 19 debugging */

2017-04-19T23:01:17Z

april 19 debugging

← Older revision		Revision as of 23:01, 19 April 2017
Line 27:		Line 27:
	Changing the port number to 9990 did not affect the outcome either. The container is still unreachable, even from the localhost. No port 9990 open anywhere, when scanning from a remote machine and when scanning from the local machine.		Changing the port number to 9990 did not affect the outcome either. The container is still unreachable, even from the localhost. No port 9990 open anywhere, when scanning from a remote machine and when scanning from the local machine.

	<s>Nothing working. No idea. Frustrating as hell.</s> Yes, of course, two minutes later everything just MAGICALLY works somehow.		<s>Nothing working. No idea. Frustrating as hell.</s>

			Yes, of course, two minutes later everything just MAGICALLY works somehow, after the fifth time trying the EXACT SAME SET OF COMMANDS.

	=References=		=References=

Admin: /* april 19 debugging */

2017-04-19T23:00:53Z

april 19 debugging

← Older revision		Revision as of 23:00, 19 April 2017
Line 27:		Line 27:
	Changing the port number to 9990 did not affect the outcome either. The container is still unreachable, even from the localhost. No port 9990 open anywhere, when scanning from a remote machine and when scanning from the local machine.		Changing the port number to 9990 did not affect the outcome either. The container is still unreachable, even from the localhost. No port 9990 open anywhere, when scanning from a remote machine and when scanning from the local machine.

	Nothing working. No idea. Frustrating as hell.		<s>Nothing working. No idea. Frustrating as hell.</s> Yes, of course, two minutes later everything just MAGICALLY works somehow.

	=References=		=References=

Admin: /* april 19 debugging */

2017-04-19T22:56:32Z

april 19 debugging

← Older revision		Revision as of 22:56, 19 April 2017
Line 26:		Line 26:

	Changing the port number to 9990 did not affect the outcome either. The container is still unreachable, even from the localhost. No port 9990 open anywhere, when scanning from a remote machine and when scanning from the local machine.		Changing the port number to 9990 did not affect the outcome either. The container is still unreachable, even from the localhost. No port 9990 open anywhere, when scanning from a remote machine and when scanning from the local machine.

			Nothing working. No idea. Frustrating as hell.

	=References=		=References=

Admin: /* april 19 debugging */

2017-04-19T22:14:19Z

april 19 debugging

← Older revision		Revision as of 22:14, 19 April 2017
Line 12:		Line 12:

	<pre>		<pre>
	$ sudo nsenter -t `docker inspect -f '{{.State.Pid}}'`		$ sudo nsenter -t `docker inspect -f '{{.State.Pid}}'` -n netstat
	</pre>		</pre>

Admin: /* april 19 debugging */

2017-04-19T21:53:45Z

april 19 debugging

← Older revision		Revision as of 21:53, 19 April 2017
Line 12:		Line 12:

	<pre>		<pre>
	sudo nsenter -t `docker inspect -f '{{.State.Pid}}'`		$ sudo nsenter -t `docker inspect -f '{{.State.Pid}}'`
	</pre>		</pre>

			Can also use docker port command to check which ports are open and exposed to the host:

			<pre>
			$ docker port container_name
			</pre>

			Went through some debugging with [[Iptables]] rules, and dropping a bunch of old crusty rules that were not being used/applied. This did not affect the firewall/connection in any way.

			Now, I'm getting really frustrated. Port 8888 simply will not open up to the outside world. Port 8081 works fine and is open from the container to the outside world (MongoExpress), but has no rules set in the firewall (incoming packets set to accept all). Same thing with port 28017, this port is also open. There is one rule for it, exactly the same as the one rule for port 8888.

			Changing the port number to 9990 did not affect the outcome either. The container is still unreachable, even from the localhost. No port 9990 open anywhere, when scanning from a remote machine and when scanning from the local machine.

	=References=		=References=