Updated Docker app implementation (markdown)

David Anderson 2024-10-26 00:57:06 -07:00
parent abe2fccda4
commit 480adccbd8
1 changed files with 5 additions and 5 deletions

@ -41,7 +41,7 @@ Here's what happens when the BOINC client runs a Docker app:
### Unix
[image](images/docker_unix.jpg)
[[images/docker_unix.jpg]]
The BOINC client runs ```docker_wrapper```
(the app version's main program)
@ -49,7 +49,7 @@ and communicates with it (pause/resume etc.)
through shared memory, as with all BOINC apps.
```docker_wrapper``` interacts with Docker
by running the Docker CLI program (using popen()).
by running the Docker CLI program (using ```popen()```).
It issues commands to list images, build an image,
and start a container, and monitor the container.
@ -57,7 +57,7 @@ and start a container, and monitor the container.
input files into the container, and output files out of the container.
It does this by either
* using the 'docker cp' command.
* using the ```docker cp``` command.
* mounting the slot and project directories in the container,
in which case the logic in the container is responsible for
finding the files
@ -68,7 +68,7 @@ This is controlled by the job config file, ```job.toml```.
### Windows
[image](images/docker_win.jpg)
[[images/docker_win.jpg]]
Based on info in ```init_data.xml```,
```docker_wrapper``` picks a WSL distro.
@ -81,7 +81,7 @@ which run in the WSL container.
These commands build images, run Docker containers, etc.
The WSL container shares the host filesystem.
The shell's current directory is that of docker_wrapper,
The shell's current directory is that of ```docker_wrapper```,
namely the job's slot directory.
Moving files in/out of the Docker container is done
the same as in the Unix case.