SiVeGCS/ray_template
6
0
Fork 1
forked from SiVeGCS/dask_template
Code Issues Pull requests Activity

steps to reproduce the container bug

Browse source
This commit is contained in:
Kerem Kayabay 2024-02-07 17:15:18 +01:00
parent 1a5970c70b
commit 966f73a51e
1 changed files with 30 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

30
reproduce_container_bug.md Normal file
View file

@ -0,0 +1,30 @@
Create the container on the login node:
```bash
export WS_DIR=$(ws_find workspace_dir) # adjust this
cd $WS_DIR
wget https://fex.hlrs.de/fop/FYaJqyzw/ray.tar # download the container archive
export CONTAINER_NAME=ray
export CONTAINER_TAG=latest
export UDOCKER_DIR="$WS_DIR/.udocker/" # to store the image layers
udocker images -l # this will create a repo the first time you use it
udocker rmi $CONTAINER_NAME:$CONTAINER_TAG # results in error since the image does not exist
udocker load -i $WS_DIR/$CONTAINER_NAME.tar $CONTAINER_NAME
rm /$WS_DIR/$CONTAINER_NAME.tar # you no longer need the tar archive
```
Allocate a CPU node:
```bash
module load bigdata/udocker/1.3.4
export WS_DIR=$(ws_find benchmarks)
udocker run --volume $WS_DIR:/workspace --volume /run/user/$PBS_JOBID/tmp:/tmp $CONTAINER_NAME
```
You should see a Python shell.
```python
import ray
# ray.init(num_cpus=4) # Works with a small number of CPUs
ray.init() # But, it can't use all the available CPUs
```