@@ -113,4 +113,30 @@ First of all, you will need to log in to OCCAM also from there, using
```
occam-login
```
and your OCCAM username and password.
\ No newline at end of file
and your OCCAM username and password (this needs to be done only once, since it will store a token in your home dir).
Now you can use the `occam-run` command to run your container:
```
occam-run <username>/docker-example
```
You will see some extra output generated by the machinery that re-builds the container in a special format and run it on one of the nodes. If you don't specify anything, like in the example above, it will use one of the "light" nodes that was set apart for testing.
```
Pulling bagnasco/docker-example from https://occam-00.ph.unito.it:5000...
Creating container from bagnasco/docker-example...
New container ID for bagnasco/docker-example is 61516d71-1d0c-33fb-ac1f-83bca4b1846c
Running 61516d71-1d0c-33fb-ac1f-83bca4b1846c in /archive/home/bagnasco/docker-example
Logfile will be 61516d71-1d0c-33fb-ac1f-83bca4b1846c.log
Remote PID for process is 299
Done.
```
The container ID (in this case `61516d71-1d0c-33fb-ac1f-83bca4b1846c`) is the unique handle you can use to interact with the running container. Any output to stderr and stdout will go, respectively, to `<id>.log` and `<id>.err` files.
As soon as the container starts on the node, the occam-run command exits: "Done" here means "done dispatching the container", not "done running". Of course in this example the container runs only for a very short time, but you can check whether it is still running or killing it with
