You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Fix paths to container installation directory
- Modify some examples to show `custom-extensions` and `EXTENSIONS_DOWNLOAD` installation options specific to the container environment.
- Add code groups to show file names
Signed-off-by: Tony Germano <tony@germano.name>
Copy file name to clipboardExpand all lines: docs/engine/plugins.md
+15-11Lines changed: 15 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,27 +69,29 @@ For environments where UI-based installation is not feasible, you can install pl
69
69
70
70
When running OIE in a Docker container, you have several options for installing plugins:
71
71
72
-
#### Option 1: Volume Mount (Recommended)
72
+
#### Example 1: Docker CLI with `custom-extensions`Volume Mount
73
73
74
-
Mount a host directory containing plugins to the container's extensions directory:
74
+
Mount a host directory containing plugin zip files to the container's `custom-extensions` directory. The container's entrypoint script will unzip and install them to the `extensions` directory prior to launching the server:
#### Example 3: Docker Compose with `EXTENSIONS_DOWNLOAD` URL
102
104
103
-
Using Docker Compose with volume mounts:
105
+
The container supports downloading a bundle of extensions from a remote web server and installing them prior to launching the server. The bundle file is a zip file that contains one or more extension zip files to be installed:
0 commit comments