Skip to content

Commit cd263ba

Browse files
committed
Update README file for fpga_crihook
Initcontainer is now built in main build process, no need to download anythin special. Added note about checking OCI hooks configuration parameter in CRI-O Fixes: #192
1 parent 2430e20 commit cd263ba

File tree

1 file changed

+5
-10
lines changed

1 file changed

+5
-10
lines changed

cmd/fpga_crihook/README.md

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -21,14 +21,9 @@ $ cd $GOPATH/src/github.com/intel/intel-device-plugins-for-kubernetes
2121
$ make fpga_crihook
2222
```
2323

24-
### Download 'Acceleration Stack for Runtime' tarball
25-
```
26-
Download a10_gx_pac_ias_1_1_pv_rte_installer.tar.gz from https://www.intel.com/content/www/us/en/programmable/solutions/acceleration-hub/downloads.html into $GOPATH/src/github.com/intel/intel-device-plugins-for-kubernetes/deployments/fpga_plugin directory
27-
```
28-
29-
### Build init container that contains CRI hook and all its dependencies:
30-
```
31-
$ cd $GOPATH/src/github.com/intel/intel-device-plugins-for-kubernetes/deployments/fpga_plugin
32-
$ ./build-initcontainer-image.sh
33-
```
24+
### Ensure that CRI-O is configured to allow OCI hooks
3425

26+
Recent versions of CRI-O are shipped with default configuration file that prevents
27+
CRI-O to discover and configure hooks automatically.
28+
For FPGA orchestration programmed mode, the OCI hooks are the key component.
29+
Thus, please make sure that in your `/etc/crio/crio.conf` parameter `hooks_dir` is either unset (to enable default search paths for OCI hooks configuration) or contains directory `/etc/containers/oci/hooks.d`

0 commit comments

Comments
 (0)