[Docs] Reflect the 0.20 changes related to working_dir and repo_dir

Author: peterschmidt85

docs/docs/concepts/services.md

@@ -597,15 +597,12 @@ resources:
 
 ### Working directory
 
-If `working_dir` is not specified, it defaults to `/workflow`.
+If `working_dir` is not specified, it defaults to the working directory set in the Docker image. For example, the [default image](#default-image) uses `/dstack/run` as its working directory.
 
-!!! info "No commands"
-    If you’re using a custom `image` without `commands`, then `working_dir` is taken from `image`.
+If the Docker image does not have a working directory set, `dstack` uses `/` as the `working_dir`.
 
 The `working_dir` must be an absolute path. The tilde (`~`) is supported (e.g., `~/my-working-dir`).
 
-<!-- TODO: In a future version, the default working directory will be taken from `image`. -->
-
 <!-- TODO: Elaborate on `entrypoint` -->
 
 ### Files
@@ -621,7 +618,7 @@ type: service
 name: llama-2-7b-service
 
 files:
-  - .:examples  # Maps the directory where `.dstack.yml` to `/workflow/examples`
+  - .:examples  # Maps the directory with `.dstack.yml` to `<working dir>/examples`
   - ~/.ssh/id_rsa:/root/.ssh/id_rsa  # Maps `~/.ssh/id_rsa` to `/root/.ssh/id_rsa`
 
 python: 3.12
@@ -640,11 +637,10 @@ resources:
 
 </div>
 
-Each entry maps a local directory or file to a path inside the container. Both local and container paths can be relative or absolute.
-
-If the local path is relative, it’s resolved relative to the configuration file. If the container path is relative, it’s resolved relative to `/workflow`.
+If the local path is relative, it’s resolved relative to the configuration file.
+If the container path is relative, it’s resolved relative to the [working directory](#working-directory).
 
-The container path is optional. If not specified, it will be automatically calculated.
+The container path is optional. If not specified, it will be automatically calculated:
 
 <!-- TODO: Add a more relevant example -->
 
@@ -655,7 +651,7 @@ type: service
 name: llama-2-7b-service
 
 files:
-  - ../examples  # Maps `examples` (the parent directory of `.dstack.yml`) to `/workflow/examples`
+  - ../examples  # Maps the parent directory of `.dstack.yml` to `<working dir>/../examples`
   - ~/.ssh/id_rsa  # Maps `~/.ssh/id_rsa` to `/root/.ssh/id_rsa`
 
 python: 3.12
@@ -681,9 +677,9 @@ resources:
 
 ### Repos
 
-Sometimes, you may want to mount an entire Git repo inside the container.
+Sometimes, you may want to clone an entire Git repo inside the container.
 
-Imagine you have a cloned Git repo containing an `examples` subdirectory with a `.dstack.yml` file:
+Imagine you have a Git repo (clonned locally) containing an `examples` subdirectory with a `.dstack.yml` file:
 
 <!-- TODO: Add a more relevant example -->
 
@@ -694,8 +690,7 @@ type: service
 name: llama-2-7b-service
 
 repos:
-  # Mounts the parent directory of `examples` (must be a Git repo)
-  #   to `/workflow` (the default working directory)
+  # Clones the repo from the parent directory (`examples/..`) to `<working dir>`
   - ..
 
 python: 3.12
@@ -714,12 +709,12 @@ resources:
 
 </div>
 
-When you run it, `dstack` fetches the repo on the instance, applies your local changes, and mounts it—so the container matches your local repo.
+When you run it, `dstack` clones the repo on the instance, applies your local changes, and mounts it—so the container matches your local repo.
 
 The local path can be either relative to the configuration file or absolute.
 
 ??? info "Repo directory"
-    By default, `dstack` mounts the repo to `/workflow` (the default working directory).
+    By default, `dstack` clones the repo to the [working directory](#working-directory).
 
     <!-- TODO: In a future version, the default working directory will come from the image, so this should be revisited. -->
 
@@ -732,8 +727,7 @@ The local path can be either relative to the configuration file or absolute.
     name: llama-2-7b-service
 
     repos:
-      # Mounts the parent directory of `examples` (must be a Git repo)
-      #   to `/my-repo`
+      # Clones the repo in the parent directory (`examples/..`) to `/my-repo`
       - ..:/my-repo
 
     python: 3.12
@@ -752,16 +746,41 @@ The local path can be either relative to the configuration file or absolute.
 
     </div>
 
-    If the path is relative, it is resolved against `working_dir`.
+    > If the repo directory is relative, it is resolved against [working directory](#working-directory).
+
+    If the repo directory is not empty, the run will fail with a runner error.  
+    To override this behavior, you can set `if_exists` to `skip`:
+
+    ```yaml
+    type: service
+    name: llama-2-7b-service   
+  
+    repos:
+      - local_path: ..
+        path: /my-repo
+        if_exists: skip
+  
+    python: 3.12
+
+    env:
+      - HF_TOKEN
+      - MODEL=NousResearch/Llama-2-7b-chat-hf
+    commands:
+      - uv pip install vllm
+      - python -m vllm.entrypoints.openai.api_server --model $MODEL --port 8000
+    port: 8000
+
+    resources:
+      gpu: 24GB
+    ```
 
 ??? info "Repo size"
     The repo size is not limited. However, local changes are limited to 2MB. 
     To avoid exceeding this limit, exclude unnecessary files using `.gitignore` or `.dstackignore`.
     You can increase the 2MB limit by setting the `DSTACK_SERVER_CODE_UPLOAD_LIMIT` environment variable.
 
 ??? info "Repo URL"
-
-    Sometimes you may want to mount a Git repo without cloning it locally. In this case, simply provide a URL in `repos`:
+    Sometimes you may want to clone a Git repo within the container without cloning it locally. In this case, simply provide a URL in `repos`:
 
     <!-- TODO: Add a more relevant example -->
 
@@ -772,7 +791,7 @@ The local path can be either relative to the configuration file or absolute.
     name: llama-2-7b-service
 
     repos:
-      # Clone the specified repo to `/workflow` (the default working directory)
+      # Clone the repo to `<working dir>`
       - https://github.com/dstackai/dstack
 
     python: 3.12
@@ -795,9 +814,9 @@ The local path can be either relative to the configuration file or absolute.
     If a Git repo is private, `dstack` will automatically try to use your default Git credentials (from
     `~/.ssh/config` or `~/.config/gh/hosts.yml`).
 
-    If you want to use custom credentials, you can provide them with [`dstack init`](../reference/cli/dstack/init.md).
+    > If you want to use custom credentials, you can provide them with [`dstack init`](../reference/cli/dstack/init.md).
 
-> Currently, you can configure up to one repo per run configuration.
+Currently, you can configure up to one repo per run configuration.
 
 ### Retry policy