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
Copy file name to clipboardExpand all lines: .devcontainer/README.md
+12-11Lines changed: 12 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -211,7 +211,7 @@ This setup allows you to use Git commands normally within the container without
211
211
### Step 5: Wait for Initialization
212
212
213
213
The container will automatically:
214
-
- Mount your local code to `/home/ubuntu/dynamo`
214
+
- Mount your local code to `/workspace`
215
215
- Run `post-create.sh` to build the project and configure the environment
216
216
217
217
If `post-create.sh` fails, you can try to debug or [submit](https://github.com/ai-dynamo/dynamo/issues) an issue on GitHub.
@@ -223,13 +223,13 @@ If `post-create.sh` fails, you can try to debug or [submit](https://github.com/a
223
223
If you make changes to Rust code and want to compile, use [cargo build](https://doc.rust-lang.org/cargo/commands/cargo-build.html). This will update Rust binaries such as dynamo-run.
224
224
225
225
```bash
226
-
cd /home/ubuntu/dynamo&& cargo build --locked --profile dev
226
+
cd /workspace&& cargo build --locked --profile dev
227
227
```
228
228
229
-
Verify that builds are in the pre-defined `dynamo/.build/target`and not `dynamo/workspace`:
229
+
Verify that builds are in the pre-defined `target`directory:
/home/ubuntu/dynamo/.build/target <-- this is the target path
232
+
/workspace/target <-- this is the target path
233
233
```
234
234
235
235
If cargo is not installed and configured properly, you will see one or more errors, such as the following:
@@ -244,22 +244,22 @@ Lastly, before pushing code to GitHub, remember to run `cargo fmt` and `cargo cl
244
244
If you make changes to Rust code and want to propagate to Python bindings then can use [maturin](https://www.maturin.rs/#usage) (pre-installed). This will update the Python bindings with your new Rust changes.
245
245
246
246
```bash
247
-
cd /home/ubuntu/dynamo/lib/bindings/python && maturin develop
247
+
cd /workspace/lib/bindings/python && maturin develop
248
248
```
249
249
250
250
## What's Inside
251
251
Development Environment:
252
252
- Rust and Python toolchains
253
253
- GPU acceleration
254
254
- VS Code or Cursor extensions for Rust and Python
255
-
- Persistent build cache in `.build/` directory enables fast incremental builds (only changed files are recompiled) via `cargo build --locked --profile dev`
255
+
- Persistent build cache in `target/` directory enables fast incremental builds (only changed files are recompiled) via `cargo build --locked --profile dev`
256
256
- Edits to files are propagated to local repo due to the volume mount
257
257
- SSH and GPG agent passthrough orchestrated by devcontainer
258
258
259
259
File Structure:
260
-
- Local dynamo repo mounts to `/home/ubuntu/dynamo`
260
+
- Local dynamo repo mounts to `/workspace`
261
261
- Python venv in `/opt/dynamo/venv`
262
-
- Build artifacts in `dynamo/.build/target`
262
+
- Build artifacts in `/workspace/target`
263
263
- Hugging Face cache preserved between sessions (either mounting your host .cache to the container, or your `HF_HOME` to `/home/ubuntu/.cache/huggingface`)
264
264
- Bash memory preserved between sessions at `/home/ubuntu/.commandhistory` using docker volume `dynamo-bashhistory`
265
265
- Precommit preserved between sessions at `/home/ubuntu/.cache/precommit` using docker volume `dynamo-precommit-cache`
VSCode will automatically port-forward and you can check them out in your browser.
@@ -376,7 +376,7 @@ If you encounter build errors or strange compilation issues, try running `cargo
376
376
If `cargo clean` doesn't resolve the issue, it is possible that some of the files were created by root (using the `run.sh` script). You can manually remove the build target by going to your host (outside the container), and remove the target:
377
377
378
378
```bash
379
-
sudo rm -rf <your dynamo path on the host machine>/.build/target
379
+
sudo rm -rf <your dynamo path on the host machine>/target
380
380
```
381
381
382
382
### Volume Corruption Issues
@@ -426,7 +426,8 @@ If you see errors like "container is not running" or "An error occurred setting
426
426
# If missing, build the dev image first, then build local-dev
427
427
export FRAMEWORK=VLLM # Replace with VLLM, SGLANG, or TRTLLM
0 commit comments