Docker/Dockerfiles - Revision history

Admin: /* Building Containers with Dockerfiles */

2017-03-30T09:51:45Z

Building Containers with Dockerfiles

← Older revision		Revision as of 09:51, 30 March 2017
Line 78:		Line 78:
	$ mkdir ~/docker		$ mkdir ~/docker
	$ cd ~/docker		$ cd ~/docker
	$ git clone https://~~github~~.com/~~taskworld~~/~~docker~~-stunnel.git		$ git clone https://charlesreid1.com:3000/docker/d-stunnel.git
	$ cd ~~docker~~-stunnel		$ cd d-stunnel
			</pre>

			Now that we are all ready:

			<pre>
	$ docker build -t cmr_stunnel .		$ docker build -t cmr_stunnel .
	</pre>		</pre>

	This creates an ~~Stunnel~~ container ready to go in docker, which can be seen by running <code>docker images</code>.		This creates an stunnel container ready to go in docker, which can be seen by running <code>docker images</code>.

	<pre>		<pre>

Admin: /* Building Containers with Dockerfiles */

2017-03-26T05:54:04Z

Building Containers with Dockerfiles

← Older revision		Revision as of 05:54, 26 March 2017
Line 81:		Line 81:
	$ cd docker-stunnel		$ cd docker-stunnel
	$ docker build -t cmr_stunnel .		$ docker build -t cmr_stunnel .
			</pre>

			This creates an Stunnel container ready to go in docker, which can be seen by running <code>docker images</code>.

			<pre>
			$ docker images
			REPOSITORY TAG IMAGE ID CREATED SIZE
			cmr_stunnel latest 2b197f506e02 59 seconds ago 219 MB
	</pre>		</pre>

Admin: /* Building Containers with Dockerfiles */

2017-03-26T05:53:25Z

Building Containers with Dockerfiles

← Older revision		Revision as of 05:53, 26 March 2017
Line 73:		Line 73:
	=Building Containers with Dockerfiles=		=Building Containers with Dockerfiles=

	~~Start by getting your~~ Dockerfile		Use the docker build command. Specify the name of the image with -t and specify the location of the Dockerfile. Here is an example, checking out a tiny repo with a single dockerfile:

			<pre>
			$ mkdir ~/docker
			$ cd ~/docker
			$ git clone https://github.com/taskworld/docker-stunnel.git
			$ cd docker-stunnel
			$ docker build -t cmr_stunnel .
			</pre>

	=Flags=		=Flags=

	{{DockerFlag}}		{{DockerFlag}}

Admin: /* Building Containers with Dockerfiles */

2017-03-26T05:52:35Z

Building Containers with Dockerfiles

← Older revision		Revision as of 05:52, 26 March 2017
Line 73:		Line 73:
	=Building Containers with Dockerfiles=		=Building Containers with Dockerfiles=

			Start by getting your Dockerfile


	=Flags=		=Flags=

	{{DockerFlag}}		{{DockerFlag}}

Admin: /* Crafting */

2017-03-26T05:47:52Z

Crafting

← Older revision		Revision as of 05:47, 26 March 2017
Line 1:		Line 1:
	The Dockerfile is where you define the commands that populate your docker container.		The Dockerfile is where you define the commands that populate your docker container.

	=Crafting=		=Crafting Dockerfiles=

	==The Philosophy==		==The Philosophy==
Line 71:		Line 71:


	~~[[Category:Docker]]~~		=Building Containers with Dockerfiles=




			=Flags=

			{{DockerFlag}}

Admin at 04:01, 26 March 2017

2017-03-26T04:01:19Z

← Older revision		Revision as of 04:01, 26 March 2017
Line 21:		Line 21:
	https://docs.docker.com/engine/reference/builder/#copy		https://docs.docker.com/engine/reference/builder/#copy

			==Finding Dockerfile examples==

			The dockerfiles used to create various docker images are usually available with the image itself and are usually quite simple. That's the idea, anyway.

			For example, here's an uncomplicated Dockerfile for an [[Stunnel]] docker container from [https://github.com/taskworld/docker-stunnel/blob/master/Dockerfile]:

			<pre>
			FROM ubuntu
			RUN apt-get update
			RUN apt-get -y install stunnel
			CMD ["stunnel"]
			</pre>

			To build custom versions, this dockerfile [https://github.com/flowplayer/docker-stunnel/blob/master/Dockerfile] might be better:

			<pre>
			# stunnel Server
			#
			# VERSION 0.0.1

			# Building from Ubuntu Precise
			FROM ubuntu:precise

			MAINTAINER Courtney Couch, courtney@moot.it

			RUN apt-get update
			RUN apt-get upgrade -y

			RUN apt-get -y install build-essential wget
			RUN apt-get -y install openssl libssl-dev

			ENV STUNNEL_VERSION 4.56

			RUN wget -O - ftp://ftp.stunnel.org/stunnel/archive/4.x/stunnel-$STUNNEL_VERSION.tar.gz \| tar -C /usr/local/src -zxv

			RUN mkdir -p /stunnel
			VOLUME ["/stunnel"]

			ADD stunnel.conf /stunnel/stunnel.conf
			ADD stunnel.pem /stunnel/stunnel.pem

			# Build stunnel
			RUN cd /usr/local/src/stunnel-$STUNNEL_VERSION && ./configure && make && make install

			EXPOSE 443

			CMD ["/usr/local/bin/stunnel", "/stunnel/stunnel.conf"]
			</pre>


	[[Category:Docker]]		[[Category:Docker]]

Admin at 07:54, 24 March 2017

2017-03-24T07:54:51Z

← Older revision		Revision as of 07:54, 24 March 2017
Line 20:		Line 20:

	https://docs.docker.com/engine/reference/builder/#copy		https://docs.docker.com/engine/reference/builder/#copy



			[[Category:Docker]]

Admin at 07:28, 24 March 2017

2017-03-24T07:28:21Z

@@ Line 1: / Line 1: @@
 The Dockerfile is where you define the commands that populate your docker container.
-The idea is to have easy to start and easy to stop services that are stateless, and don't "expect" stuff. (Not sure I understand that exactly, but ok.)
+=Crafting=
 Web app stack example: LAMP would implement Apache as one container, MySQL as another, and PHP as another (well, maybe A+P as one.)
@@ Line 8: / Line 12: @@
 Keep em clean, keep em modular.

Admin: Created page with "The Dockerfile is where you define the commands that populate your docker container. The idea is to have easy to start and easy to stop services that are stateless, and don't..."

2017-03-24T07:13:26Z

Created page with "The Dockerfile is where you define the commands that populate your docker container. The idea is to have easy to start and easy to stop services that are stateless, and don't..."

New page

The Dockerfile is where you define the commands that populate your docker container.

The idea is to have easy to start and easy to stop services that are stateless, and don't "expect" stuff. (Not sure I understand that exactly, but ok.)

Web app stack example: LAMP would implement Apache as one container, MySQL as another, and PHP as another (well, maybe A+P as one.)

Maybe one container for a cache, too.

Keep em clean, keep em modular.