Skip to content

Commit 7a92d45

Browse files
fix: change docs to recommend mlflow-data volume mount as rw (#379)
#### Description of changes Updated documented volume mount options for mlflow-data to explicitly request read-write access. Likely needed due to recent changes around user handling in Tesseract. #### Testing done Local Co-authored-by: Alessandro Angioi <[email protected]>
1 parent f3fd4dc commit 7a92d45

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/content/using-tesseracts/advanced.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,13 +49,13 @@ Launch the `metrics` example Tesseract with the the following volume mount and `
4949
MacOS and Windows with Docker Desktop requires the `host.docker.internal` hostname to access services running on the host machine:
5050

5151
```bash
52-
tesseract serve --env=TESSERACT_MLFLOW_TRACKING_URI=http://host.docker.internal:5000 --volume mlflow-data:/mlflow-data metrics
52+
tesseract serve --env=TESSERACT_MLFLOW_TRACKING_URI=http://host.docker.internal:5000 --volume mlflow-data:/mlflow-data:rw metrics
5353
```
5454

5555
For Linux, set your Tesseracts to use the host network and access the MLflow server at `localhost`:
5656

5757
```bash
58-
tesseract serve --env=TESSERACT_MLFLOW_TRACKING_URI=http://localhost:5000 --network=host --volume mlflow-data:/mlflow-data metrics
58+
tesseract serve --env=TESSERACT_MLFLOW_TRACKING_URI=http://localhost:5000 --network=host --volume mlflow-data:/mlflow-data:rw metrics
5959
```
6060

6161
The same options apply when executing Tesseracts through `tesseract run`.

0 commit comments

Comments
 (0)