Docker Containers - Revision history

Joesterle at 13:12, 28 October 2025

2025-10-28T13:12:08Z

2025-10-28T13:09:47Z

← Older revision		Revision as of 15:09, 28 October 2025
Line 14:		Line 14:

	Cluster node IPs:		Cluster node IPs:
	* eul1: 172.29.0.~~148~~		* eul1: 172.29.0.161
	* eul2: 172.29.0.~~149~~		* eul2: 172.29.0.162
	* eul3: 172.29.0.~~150~~		* eul3: 172.29.0.163
	* eul4: 172.29.0.~~184~~		* eul4: 172.29.0.164
	* eul5: 172.29.0.~~185~~		* eul5: 172.29.0.165
	* ~~gpu4~~: 172.29.0.~~54 (Use only for GPU computation)~~		* eul5: 172.29.0.166
			* gpu1: 172.29.0.51
			* gpu2: 172.29.0.52<br />
	If you have troubles with the ssh key authentication run <pre> ssh-keygen -R "hostname"</pre>		If you have troubles with the ssh key authentication run <pre> ssh-keygen -R "hostname"</pre>
	(with hostname = eulX) and accept the new key when you ssh to the respective node.		(with hostname = eulX) and accept the new key when you ssh to the respective node.

2023-12-20T10:10:15Z

← Older revision		Revision as of 12:10, 20 December 2023
Line 19:		Line 19:
	* eul4: 172.29.0.184		* eul4: 172.29.0.184
	* eul5: 172.29.0.185		* eul5: 172.29.0.185
	* gpu4: 172.29.0.54 (~~Shared among multiple CIN groups!~~)		* gpu4: 172.29.0.54 (Use only for GPU computation)

2023-12-20T10:09:24Z

Accessing the cluster nodes

← Older revision		Revision as of 12:09, 20 December 2023
Line 17:		Line 17:
	* eul2: 172.29.0.149		* eul2: 172.29.0.149
	* eul3: 172.29.0.150		* eul3: 172.29.0.150
	* ~~gpu3~~: 172.29.0.~~53 (Shared among multiple CIN groups!)~~		* eul4: 172.29.0.184
			* eul5: 172.29.0.185
	* gpu4: 172.29.0.54 (Shared among multiple CIN groups!)		* gpu4: 172.29.0.54 (Shared among multiple CIN groups!)

2023-01-10T16:12:13Z

← Older revision		Revision as of 18:12, 10 January 2023
Line 34:		Line 34:
	To start a new container call the following command replacing the arguments with meaningful values:		To start a new container call the following command replacing the arguments with meaningful values:
	<pre>		<pre>
	python agte-docker run -ti --jupyterport pppp --~~jupyterpass~~ some_password --name container_name_suffix -v /gpfs01/euler/data/Data:/gpfs01/euler/data/Data:ro -v /gpfs01/euler/data/Resources:/gpfs01/euler/data/Resources:ro berenslab/datajoint		python agte-docker run -d --jupyterport pppp --jupytertoken some_password --name container_name_suffix -v /gpfs01/euler/data/Data:/gpfs01/euler/data/Data:ro -v /gpfs01/euler/data/Resources:/gpfs01/euler/data/Resources:ro berenslab/datajoint
	</pre>		</pre>

Line 42:		Line 42:
	Calling the script will look something like this. You have use a script of the group you are in (AG Euler: agte_xx, AG Berens. agpb_xx)		Calling the script will look something like this. You have use a script of the group you are in (AG Euler: agte_xx, AG Berens. agpb_xx)
	<pre>		<pre>
	python agte-docker run -ti --jupyterport pppp --~~jupyterpass~~ some_password --name container_name_suffix berenslab/datajoint		python agte-docker run -d --jupyterport pppp --jupytertoken some_password --name container_name_suffix berenslab/datajoint
	</pre>		</pre>

2022-11-28T09:57:36Z

← Older revision		Revision as of 11:57, 28 November 2022
Line 17:		Line 17:
	* eul2: 172.29.0.149		* eul2: 172.29.0.149
	* eul3: 172.29.0.150		* eul3: 172.29.0.150
	* gpu3: 172.29.0.53		* gpu3: 172.29.0.53 (Shared among multiple CIN groups!)
	* gpu4: 172.29.0.54		* gpu4: 172.29.0.54 (Shared among multiple CIN groups!)

2022-11-28T09:57:09Z

Accessing the cluster nodes

← Older revision		Revision as of 11:57, 28 November 2022
Line 14:		Line 14:

	Cluster node IPs:		Cluster node IPs:
	* eul1 172.29.0.148		* eul1: 172.29.0.148
	* eul2 172.29.0.149		* eul2: 172.29.0.149
	* eul3 172.29.0.150		* eul3: 172.29.0.150
			* gpu3: 172.29.0.53
			* gpu4: 172.29.0.54


	If you have troubles with the ssh key authentication run <pre> ssh-keygen -R "hostname"</pre>		If you have troubles with the ssh key authentication run <pre> ssh-keygen -R "hostname"</pre>

2022-11-21T15:38:03Z

Starting docker containers

← Older revision		Revision as of 17:38, 21 November 2022
Line 52:		Line 52:

	If you want to use a GPU you want to ensure that you are the only one on a specific GPU and that your calculations use only one of the two GPUs of the node. Therefore run the script with		If you want to use a GPU you want to ensure that you are the only one on a specific GPU and that your calculations use only one of the two GPUs of the node. Therefore run the script with
	<pre>GPU=X python agte-docker run -ti --jupyterport pppp --jupyterpass some_password --name container_name_suffix berenslab/datajoint</pre>		<pre>GPU=X python agte-docker run -d --jupyterport pppp --jupyterpass some_password --name container_name_suffix berenslab/datajoint</pre>
	with either <code>GPU=0</code> or <code>GPU=1</code>.		with either <code>GPU=0</code> or <code>GPU=1</code>.

Line 59:		Line 59:
	To start a container in interactive mode with bash and no jupyter notebook server call		To start a container in interactive mode with bash and no jupyter notebook server call
	<pre>		<pre>
	python agte-docker run -ti --jupyterport pppp --name container_name berenslab/datajoint bash		python agte-docker run -d --jupyterport pppp --name container_name berenslab/datajoint bash
	</pre>		</pre>

2022-04-05T14:47:26Z

← Older revision		Revision as of 16:47, 5 April 2022
Line 31:		Line 31:
	To start a new container call the following command replacing the arguments with meaningful values:		To start a new container call the following command replacing the arguments with meaningful values:
	<pre>		<pre>
	python agte-docker run -ti --jupyterport pppp --jupyterpass some_password --name container_name_suffix -v /gpfs01/euler/data/Data:/gpfs01/euler/data/Data:ro -v /gpfs01/euler/data/Resources~~/Stimulus~~:/gpfs01/euler/data/Resources~~/Stimulus~~:ro berenslab/datajoint		python agte-docker run -ti --jupyterport pppp --jupyterpass some_password --name container_name_suffix -v /gpfs01/euler/data/Data:/gpfs01/euler/data/Data:ro -v /gpfs01/euler/data/Resources:/gpfs01/euler/data/Resources:ro berenslab/datajoint
	</pre>		</pre>

2022-03-28T09:49:22Z

Starting docker containers

← Older revision		Revision as of 11:49, 28 March 2022
Line 31:		Line 31:
	To start a new container call the following command replacing the arguments with meaningful values:		To start a new container call the following command replacing the arguments with meaningful values:
	<pre>		<pre>
	python agte-docker run -ti --jupyterport ~~6789~~ --jupyterpass some_password --name container_name_suffix -v /gpfs01/euler/data/Data:/gpfs01/euler/data/Data:ro -v /gpfs01/euler/data/Resources/Stimulus:/gpfs01/euler/data/Resources/Stimulus:ro berenslab/datajoint		python agte-docker run -ti --jupyterport pppp --jupyterpass some_password --name container_name_suffix -v /gpfs01/euler/data/Data:/gpfs01/euler/data/Data:ro -v /gpfs01/euler/data/Resources/Stimulus:/gpfs01/euler/data/Resources/Stimulus:ro berenslab/datajoint
	</pre>		</pre>