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
- handle trying uninitalized rooz gracefully - on creating a workspace in an uninitiated rooz: thread 'main' (15677) panicked at src/api/crypt.rs:9:55: called `Option::unwrap()` on a `None` value note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
- stop chowning on rooz enter - redesign - it causes issues when a sidecar writes to a volume and then the workspace container user takes ownership making the sidecar user unable to access the dir. Let's consider chowning on creation instead and think what consequences it would have
- mounting data into two containers at different paths only keeps the same one (making the file missing in other containers), let's change the paths to be hashes of the data entry key, or just the names of the data entry keys to make sure they're consistent across containers rather than using target mount paths.
- sidecar-install: stop injecting the sidecar env into the install stage container & the resulting runtime image
- include the runtime images created by sidecar-install in the workspace removal so they're cleaned up (on remove) and rebuilt (on update)
- handle trying uninitalized rooz gracefully - on creating a workspace in an uninitiated rooz:
thread 'main' (15677) panicked at src/api/crypt.rs:9:55: called `Option::unwrap()` on a `None` value note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace- stop chowning on
rooz enter- redesign - it causes issues when a sidecar writes to a volume and then the workspace container user takes ownership making the sidecar user unable to access the dir. Let's consider chowning on creation instead and think what consequences it would have- mounting data into two containers at different paths only keeps the same one (making the file missing in other containers), let's change the paths to be hashes of the data entry key, or just the names of the data entry keys to make sure they're consistent across containers rather than using target mount paths.
- sidecar-install: stop injecting the sidecar env into the install stage container & the resulting runtime image
- include the runtime images created by sidecar-install in the workspace removal so they're cleaned up (on remove) and rebuilt (on update)
fix: sidecar-install: include images in prune
- allow configuring shell for sidecars