Docker (deprecated) - Revision history

Joesterle: Joesterle moved page Docker to Docker (deprecated) over redirect

2022-03-28T08:46:13Z

Joesterle moved page Docker to Docker (deprecated) over redirect

← Older revision	Revision as of 08:46, 28 March 2022
(No difference)

Joesterle: Joesterle moved page Docker (deprecated) to Docker over redirect

2022-03-28T08:37:15Z

Joesterle moved page Docker (deprecated) to Docker over redirect

← Older revision	Revision as of 08:37, 28 March 2022
(No difference)

Joesterle: Joesterle moved page Docker to Docker (deprecated): deprecated

2022-03-28T08:36:33Z

Joesterle moved page Docker to Docker (deprecated): deprecated

← Older revision	Revision as of 08:36, 28 March 2022
(No difference)

Lrogerson: /* How do I build my own docker containers? */

2015-10-13T15:19:16Z

How do I build my own docker containers?

← Older revision		Revision as of 15:19, 13 October 2015
Line 23:		Line 23:
	\|-		\|-
	\| -e DISPLAY=$DISPLAY\|\|Needed for plotting in Jupyter		\| -e DISPLAY=$DISPLAY\|\|Needed for plotting in Jupyter
			\|-
			\| -v\|\|Mount volume, see below
	\|-		\|-
	\| --help\|\|Show different tag options for given command		\| --help\|\|Show different tag options for given command
	\|-
	~~\| -v\|\|Mount volume, see below~~
	\|} </blockquote>		\|} </blockquote>

Lrogerson: /* How do I build my own docker containers? */

2015-10-13T15:18:54Z

How do I build my own docker containers?

← Older revision		Revision as of 15:18, 13 October 2015
Line 8:		Line 8:

	==How do I build my own docker containers?==		==How do I build my own docker containers?==
	New docker containers can be built using the command: <blockquote>docker run [~~...~~]</blockquote> For example, to build a new scipyserver called 'miranda', forwarded to port 1948 on localhost with the password 'uranus', you would enter: <blockquote>docker run -d -p 1948:8888 --name miranda -e "PASSWORD=uranus" -e DISPLAY=$DISPLAY ipython/scipyserver</blockquote> Each of the -tags has a unique function in building the server. The last entry specifies the image from which the container is built, in this case an ipython server. You can find more images over at [https://hub.docker.com/ Dockerhub].		New docker containers can be built using the command: <blockquote>docker run [-tags] [imageName]</blockquote> For example, to build a new scipyserver called 'miranda', forwarded to port 1948 on localhost with the password 'uranus', you would enter: <blockquote>docker run -d -p 1948:8888 --name miranda -e "PASSWORD=uranus" -e DISPLAY=$DISPLAY ipython/scipyserver</blockquote> Each of the -tags has a unique function in building the server. The last entry specifies the image from which the container is built, in this case an ipython server. You can find more images over at [https://hub.docker.com/ Dockerhub].

	<blockquote>		<blockquote>

Lrogerson: /* What is docker? */

2015-10-13T13:36:05Z

What is docker?

← Older revision		Revision as of 13:36, 13 October 2015
Line 1:		Line 1:
	==What is docker?==		==What is docker?==

	Docker is a platform for running virtual machines called ''containers''. These are functionally analogous to the operating systems on a computer, though you can run them from within your operating system. They are useful because they create lightweight, customisable environments within which you can run software. This is particularly helpful when you have programs which have very particular dependencies, or require a linux base installation in order to function correctly. You can read more about ~~docker~~ [https://www.docker.com/whatisdocker here].		Docker is a platform for running virtual machines called ''containers''. These are functionally analogous to the operating systems on a computer, though you can run them from within your operating system. They are useful because they create lightweight, customisable environments within which you can run software. This is particularly helpful when you have programs which have very particular dependencies, or require a linux base installation in order to function correctly. You can read more about Docker [https://www.docker.com/whatisdocker here].

	==What do we use docker for?==		==What do we use docker for?==

Lrogerson: /* How do I build my own docker containers? */

2015-10-13T10:32:36Z

How do I build my own docker containers?

← Older revision		Revision as of 10:32, 13 October 2015
Line 8:		Line 8:

	==How do I build my own docker containers?==		==How do I build my own docker containers?==
	~~For a more thorough walkthough, see the official [https://docs.docker.com/linux/started/ Getting Started] documentation.~~ New docker containers can be built using the command: <blockquote>docker run [...]</blockquote> For example, to build a new scipyserver called 'miranda', forwarded to port 1948 on localhost with the password 'uranus', you would enter: <blockquote>docker run -d -p 1948:8888 --name miranda -e "PASSWORD=uranus" -e DISPLAY=$DISPLAY ipython/scipyserver</blockquote> Each of the -tags has a unique function in building the server. The last entry specifies the image from which the container is built, in this case an ipython server. You can find more images over at [https://hub.docker.com/ Dockerhub].		New docker containers can be built using the command: <blockquote>docker run [...]</blockquote> For example, to build a new scipyserver called 'miranda', forwarded to port 1948 on localhost with the password 'uranus', you would enter: <blockquote>docker run -d -p 1948:8888 --name miranda -e "PASSWORD=uranus" -e DISPLAY=$DISPLAY ipython/scipyserver</blockquote> Each of the -tags has a unique function in building the server. The last entry specifies the image from which the container is built, in this case an ipython server. You can find more images over at [https://hub.docker.com/ Dockerhub].

	<blockquote>		<blockquote>
Line 30:		Line 30:

	Data stored in docker containers is transient and is lost when the container is deleted. In order to set the containers so that they can access volumes on the host system and persist their content after they are deleted, we have to use additional tags to mount directories in the container to directories on the host system. Here is an example of this for another ipython server:<blockquote>docker run -v ~/Notebooks:/notebooks/Notebooks -v ~/Data:/notebooks/Data:ro -v /tmp/.X11-unix:/tmp/.X11-unix:ro ipython/scipyserver</blockquote> Here, three different directories have been mounted: a volume which the container can write to, under notebooks/Notebooks, a volume which the container can read, under notebooks/Data (the :ro tag specifies read only), and a further folder used for X11 forwarding, which is necessary for getting figures in the Jupiter server.		Data stored in docker containers is transient and is lost when the container is deleted. In order to set the containers so that they can access volumes on the host system and persist their content after they are deleted, we have to use additional tags to mount directories in the container to directories on the host system. Here is an example of this for another ipython server:<blockquote>docker run -v ~/Notebooks:/notebooks/Notebooks -v ~/Data:/notebooks/Data:ro -v /tmp/.X11-unix:/tmp/.X11-unix:ro ipython/scipyserver</blockquote> Here, three different directories have been mounted: a volume which the container can write to, under notebooks/Notebooks, a volume which the container can read, under notebooks/Data (the :ro tag specifies read only), and a further folder used for X11 forwarding, which is necessary for getting figures in the Jupiter server.

			For a more thorough walkthough, see the official [https://docs.docker.com/linux/started/ Getting Started] documentation.

Lrogerson: /* What do we use docker for? */

2015-10-13T10:32:21Z

What do we use docker for?

← Older revision		Revision as of 10:32, 13 October 2015
Line 7:		Line 7:
	The Euler group is currently using docker to host [[Jupyter_Notebooks\|our two Jupyter notebook servers]], though in the past we have also used it for hosting a MySQL server. To see what containers are currently running, ssh into 'cn31' and enter the command: <blockquote>docker ps</blockquote> This will return a list of the currently active docker containers, the images they are built from, how long they have been online and what ports they are forwarded to.		The Euler group is currently using docker to host [[Jupyter_Notebooks\|our two Jupyter notebook servers]], though in the past we have also used it for hosting a MySQL server. To see what containers are currently running, ssh into 'cn31' and enter the command: <blockquote>docker ps</blockquote> This will return a list of the currently active docker containers, the images they are built from, how long they have been online and what ports they are forwarded to.

	New docker containers can be built using the command: <blockquote>docker run [...]</blockquote> For example, to build a new scipyserver called 'miranda', forwarded to port 1948 on localhost with the password 'uranus', you would enter: <blockquote>docker run -d -p 1948:8888 --name miranda -e "PASSWORD=uranus" -e DISPLAY=$DISPLAY ipython/scipyserver</blockquote> Each of the -tags has a unique function in building the server. The last entry specifies the image from which the container is built, in this case an ipython server. You can find more images over at [https://hub.docker.com/ Dockerhub].		==How do I build my own docker containers?==
			For a more thorough walkthough, see the official [https://docs.docker.com/linux/started/ Getting Started] documentation. New docker containers can be built using the command: <blockquote>docker run [...]</blockquote> For example, to build a new scipyserver called 'miranda', forwarded to port 1948 on localhost with the password 'uranus', you would enter: <blockquote>docker run -d -p 1948:8888 --name miranda -e "PASSWORD=uranus" -e DISPLAY=$DISPLAY ipython/scipyserver</blockquote> Each of the -tags has a unique function in building the server. The last entry specifies the image from which the container is built, in this case an ipython server. You can find more images over at [https://hub.docker.com/ Dockerhub].

	<blockquote>		<blockquote>

Lrogerson: /* What do we use docker for? */

2015-10-13T10:30:40Z

What do we use docker for?

← Older revision		Revision as of 10:30, 13 October 2015
Line 25:		Line 25:
	\| --help\|\|Show different tag options for given command		\| --help\|\|Show different tag options for given command
	\|-		\|-
	\| -v		\| -v\|\|Mount volume, see below
	\|Mount volume, see below
	\|} </blockquote>		\|} </blockquote>

	Data stored in docker containers is transient and is lost when the container is deleted. In order to set the containers so that they can access volumes on the host system and persist their content after they are deleted, we have to use additional tags to mount directories in the container to directories on the host system. Here is an example of this for another ipython server:<blockquote>docker run -v ~/Notebooks:/notebooks/Notebooks -v ~/Data:/notebooks/Data:ro -v /tmp/.X11-unix:/tmp/.X11-unix:ro ipython/scipyserver</blockquote> Here, three different directories have been mounted: a volume which the container can write to, under notebooks/Notebooks, a volume which the container can read, under notebooks/Data (the :ro tag specifies read only), and a further folder used for X11 forwarding, which is necessary for getting figures in the Jupiter server.		Data stored in docker containers is transient and is lost when the container is deleted. In order to set the containers so that they can access volumes on the host system and persist their content after they are deleted, we have to use additional tags to mount directories in the container to directories on the host system. Here is an example of this for another ipython server:<blockquote>docker run -v ~/Notebooks:/notebooks/Notebooks -v ~/Data:/notebooks/Data:ro -v /tmp/.X11-unix:/tmp/.X11-unix:ro ipython/scipyserver</blockquote> Here, three different directories have been mounted: a volume which the container can write to, under notebooks/Notebooks, a volume which the container can read, under notebooks/Data (the :ro tag specifies read only), and a further folder used for X11 forwarding, which is necessary for getting figures in the Jupiter server.

Lrogerson: /* What do we use docker for? */

2015-10-13T10:30:29Z

What do we use docker for?

← Older revision		Revision as of 10:30, 13 October 2015
Line 25:		Line 25:
	\| --help\|\|Show different tag options for given command		\| --help\|\|Show different tag options for given command
	\|-		\|-
	\|-v		\| -v
	\|Mount volume, see below		\|Mount volume, see below
	\|} </blockquote>		\|} </blockquote>

	Data stored in docker containers is transient and is lost when the container is deleted. In order to set the containers so that they can access volumes on the host system and persist their content after they are deleted, we have to use additional tags to mount directories in the container to directories on the host system. Here is an example of this for another ipython server:<blockquote>docker run -v ~/Notebooks:/notebooks/Notebooks -v ~/Data:/notebooks/Data:ro -v /tmp/.X11-unix:/tmp/.X11-unix:ro ipython/scipyserver</blockquote> Here, three different directories have been mounted: a volume which the container can write to, under notebooks/Notebooks, a volume which the container can read, under notebooks/Data (the :ro tag specifies read only), and a further folder used for X11 forwarding, which is necessary for getting figures in the Jupiter server.		Data stored in docker containers is transient and is lost when the container is deleted. In order to set the containers so that they can access volumes on the host system and persist their content after they are deleted, we have to use additional tags to mount directories in the container to directories on the host system. Here is an example of this for another ipython server:<blockquote>docker run -v ~/Notebooks:/notebooks/Notebooks -v ~/Data:/notebooks/Data:ro -v /tmp/.X11-unix:/tmp/.X11-unix:ro ipython/scipyserver</blockquote> Here, three different directories have been mounted: a volume which the container can write to, under notebooks/Notebooks, a volume which the container can read, under notebooks/Data (the :ro tag specifies read only), and a further folder used for X11 forwarding, which is necessary for getting figures in the Jupiter server.