Docker/Basics - Revision history

Admin: /* Troubleshooting */

2018-01-31T08:27:45Z

Troubleshooting

2018-01-31T08:27:30Z

Troubleshooting

2018-01-31T08:03:17Z

Exposing Ports

← Older revision		Revision as of 08:03, 31 January 2018
Line 218:		Line 218:
	</pre>		</pre>

	The Docker User Guide explains in detail how to manipulate ports in Docker.		The Docker User Guide explains in detail how to manipulate ports in Docker: https://docs.docker.com/engine/userguide/networking/default_network/binding/

	===Httpd container: bind to private, local host port===		===Httpd container: bind to private, local host port===

2018-01-31T08:02:36Z

Ports

← Older revision		Revision as of 08:02, 31 January 2018
Line 196:		Line 196:
	<pre>		<pre>
	docker run -p HOST_IP:HOST_PORT:CONTAINER_PORT		docker run -p HOST_IP:HOST_PORT:CONTAINER_PORT
			</pre>

			to expose a port on the host machine to local requests:

			<pre>
	docker run -p 127.0.0.1:80:8080 ubuntu bash		docker run -p 127.0.0.1:80:8080 ubuntu bash
	</pre>		</pre>

	This binds port 8080 of the container to port 80 on 127.0.0.1 of the host machine. You can also leave out the host IP:		This binds port 8080 of the container to port 80 on 127.0.0.1 of the host machine.

			Similarly, if you are connected to a VPN subnet like 10.6.0.x,

			<pre>
			docker run -p 10.6.0.1:80:8080 ubuntu bash
			</pre>

			You can also leave out the host IP:

	<pre>		<pre>
Line 240:		Line 252:

	[[Image:DockerHttpdPublicPort.png\|300px]]		[[Image:DockerHttpdPublicPort.png\|300px]]





	=Troubleshooting=		=Troubleshooting=

2017-09-23T19:19:04Z

Flags

2017-09-23T19:00:16Z

Httpd container: bind to public host port

2017-09-23T18:59:00Z

Volumes

← Older revision		Revision as of 18:59, 23 September 2017
Line 39:		Line 39:
	$ docker run -v /doesnt/exist:/foo -w /foo -i -t ubuntu bash		$ docker run -v /doesnt/exist:/foo -w /foo -i -t ubuntu bash
	</pre>		</pre>

			===Read-Only Volumes===

	Read only control can be set on volumes as well: <code>--read-only</code> flag. This flag makes the entire contents of the container's root filesystem read-only, except for volumes mounted with the <code>-v</code> flag. To illustrate:		Read only control can be set on volumes as well: <code>--read-only</code> flag. This flag makes the entire contents of the container's root filesystem read-only, except for volumes mounted with the <code>-v</code> flag. To illustrate:

2017-03-30T23:14:51Z

Exposing Ports

← Older revision		Revision as of 23:14, 30 March 2017
Line 195:		Line 195:
	docker run -p HOST_IP:HOST_PORT:CONTAINER_PORT		docker run -p HOST_IP:HOST_PORT:CONTAINER_PORT

	docker run -p 127.0.0.1:80:8080 ubuntu bash		docker run -p 127.0.0.1:80:8080 ubuntu bash
	</pre>		</pre>

	This binds port 8080 of the container to port 80 on 127.0.0.1 of the host machine. ~~The Docker User Guide explains in detail how to manipulate ports in Docker.~~		This binds port 8080 of the container to port 80 on 127.0.0.1 of the host machine. You can also leave out the host IP:

			<pre>
			docker run -p 80:8080 ubuntu bash
			</pre>

			The Docker User Guide explains in detail how to manipulate ports in Docker.

	===Httpd container: bind to private, local host port===		===Httpd container: bind to private, local host port===

2017-03-25T22:34:04Z

Listing all/running containers

← Older revision		Revision as of 22:34, 25 March 2017
Line 105:		Line 105:
	<pre>		<pre>

	~~charles @ rojo via 104.200.154.88 [ 2017-03-24 - 05:17:03 - 57 ] ~~~ $ docker ps		$ docker ps
	CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES		CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

	~~charles @ rojo via 104.200.154.88 [ 2017-03-24 - 05:18:26 - 58 ] ~~~ $ docker ps -a		$ docker ps -a
	CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES		CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
	d6a0776634d4 hello-world:latest "/hello" About a minute ago Exited (0) About a minute ago cranky_blackwell		d6a0776634d4 hello-world:latest "/hello" About a minute ago Exited (0) About a minute ago cranky_blackwell

2017-03-25T02:52:37Z

Volumes

← Older revision		Revision as of 02:52, 25 March 2017
Line 40:		Line 40:
	</pre>		</pre>

	Read only control can be set on volumes as well: <code>--read-only</code> flag.		Read only control can be set on volumes as well: <code>--read-only</code> flag. This flag makes the entire contents of the container's root filesystem read-only, except for volumes mounted with the <code>-v</code> flag. To illustrate:

	<pre>		<pre>
	$ docker run -t -i -v /~~var~~/~~run~~/~~docker.sock~~:/~~var/run/docker.sock~~ -v ~~/path/to/static~~-docker-~~binary:~~/~~usr~~/~~bin~~/~~docker busybox sh~~		$ # this will not work, because /canttouchthis is part of the container's root filesystem
			$ docker run -t --read-only -v /icanwrite busybox touch /canttouchthis
			touch: /canttouchthis: Read-only file system

			$ # this will work, because /icanwrite is mounted with -v and is not read-only
			$ docker run --read-only -v /icanwrite busybox touch /icanwrite/here

			$ # no error, no poblem!
	</pre>		</pre>