ITEP-87867 Information about docker compose profile

dlstreamer-pipeline-server/README.md

@@ -31,8 +31,8 @@ Following are the step-by-step instructions for enabling the out-of-box scenes i
    If you have already deployed Intel® SceneScape, use:
 
    ```sh
-   docker compose down --remove-orphans
-   docker compose up -d
+   docker compose --profile controller down --remove-orphans
+   docker compose --profile controller up -d
    ```
 
 ## Running on GPU

docs/user-guide/building-a-scene/how-to-configure-a-hierarchy-of-scenes.md

@@ -80,7 +80,7 @@ _Figure 5: ntpserver config for DL Streamer Pipeline in `pipeline-config.json`._
 
 ```bash
 ./deploy.sh
-docker compose down --remove-orphans
+docker compose --profile controller down --remove-orphans
 rm manager/secrets/ca/* manager/secrets/certs/*
 make -C tools/certificates/ deploy-certificates CERTPASS=<random-string>
 ```
@@ -91,7 +91,7 @@ make -C tools/certificates/ deploy-certificates CERTPASS=<random-string>
 
 ```bash
 ./deploy.sh
-docker compose down --remove-orphans
+docker compose --profile controller down --remove-orphans
 rm manager/secrets/ca/* manager/secrets/certs/*
 # Copy parent secrets:
 scp parent:/path-to-scenescape-repo/manager/secrets/ca/scenescape-ca.key ./manager/secrets/ca/

docs/user-guide/building-a-scene/how-to-create-new-scene.md

@@ -114,10 +114,10 @@ Using a mapping tool, it is possible to measure various distances between points
 From the Intel® SceneScape working directory on the scene controller, bring up the system with the new configuration:
 
 ```bash
-docker compose up
+docker compose --profile controller up
 ```
 
-If you are using Configuration 2, also run `docker compose up` on each additional computer.
+If you are using Configuration 2, also run `docker compose --profile controller up` on each additional computer.
 
 Launch Intel® SceneScape and log in. Create a new scene by clicking on "Scenes" in the navigation menu, and then clicking on "+ New Scene". Give your scene a name, select your floor plan file, and enter the scene's scale. Using the above parking lot example, it might look something like this:
 

docs/user-guide/building-a-scene/how-to-generate-scene-map.md

@@ -240,15 +240,17 @@ For optimal mesh generation results:
 To stop all Intel® SceneScape services:
 
 ```bash
-docker compose down
+docker compose --profile controller --profile experimental down
 ```
 
 To stop services and remove volumes (this will delete all data):
 
 ```bash
-docker compose down -v
+docker compose --profile controller --profile experimental down -v
 ```
 
+> **Note:** The `--profile` flags must match those used when starting the services. If you only started with `--profile controller`, omit `--profile experimental`.
+
 ---
 
 ## Troubleshooting

docs/user-guide/calibrating-cameras/how-to-autocalibrate-cameras-using-apriltags.md

@@ -120,8 +120,8 @@ autocalibration:
 6. Restart Intel® SceneScape:
 
 ```bash
-docker compose down
-docker compose up
+docker compose --profile controller down
+docker compose --profile controller up
 ```
 
 7. Navigate to the camera page and click **Auto Calibrate**.

docs/user-guide/get-started.md

@@ -133,15 +133,17 @@ Enter "admin" for the user name and the value you typed earlier for SUPASS.
 To stop the containers, use the following command in the project directory:
 
 ```console
-docker compose down --remove-orphans
+docker compose --profile controller down --remove-orphans
 ```
 
+> **Note:** The Scene Controller runs under the `controller` Docker Compose profile when deployed with `make demo`. Without passing `--profile controller` to the down command, the controller container will remain running. If you encounter leftover containers, network, or volumes after `docker compose down`, ensure you include `--profile controller`.
+
 ### Starting the System
 
 To start after the first time, use the following command in the project directory:
 
 ```console
-docker compose up -d
+docker compose --profile controller up -d
 ```
 
 ## Summary

docs/user-guide/other-topics/how-to-enable-reidentification.md

@@ -83,7 +83,7 @@ This reidentification-specific configuration uses a vision pipeline that include
    Launch the updated stack:
 
    ```bash
-   docker compose up
+   docker compose --profile controller up
    ```
 
 **Expected Result**: Intel® SceneScape starts with ReID enabled and begins assigning UUIDs based on visual similarity.
@@ -124,7 +124,7 @@ retail-config:
 4. **Restart the System**:
 
    ```bash
-   docker compose up --build
+   docker compose --profile controller up --build
    ```
 
 **Expected Result**: Intel® SceneScape runs without ReID and no visual feature matching is performed.
@@ -166,9 +166,9 @@ When an object is first detected, it is assigned a UUID and no similarity score.
 To apply changes:
 
 ```bash
-docker compose down
+docker compose --profile controller down
 make -C docker
-docker compose up --build
+docker compose --profile controller up --build
 ```
 
 ---

docs/user-guide/other-topics/how-to-integrate-geti-trained-model.md

@@ -65,8 +65,8 @@ This guide assumes familiarity with basic machine learning and Docker concepts.
 3. **Deploy Intel® SceneScape**:
 
    ```bash
-   docker compose down --remove-orphans
-   docker compose up -d
+   docker compose --profile controller down --remove-orphans
+   docker compose --profile controller up -d
    ```
 
    Log into the Intel® SceneScape UI and verify that bounding boxes appear correctly.