When Devbox detects a user doesn't have Nix installed, it will offer to install it for the user. If a user allows this action, then terminates their shell and opens a new one, the Nix binary is still unavailable. Nix's install script adds its path to .profile but no shell startup scripts are run when VS Code Remote is started in WSL: https://code.visualstudio.com/docs/remote/wsl#_advanced-environment-setup-script
As a result, the auto shell feature of the VS Code Devbox extension also doesn't work giving Error: We found a /nix directory but nix binary is not in your PATH. Try restarting your terminal and running devbox again. If after restarting you still get this message it's possible nix setup is missing from your shell rc file. See https://github.com/NixOS/nix/issues/3616#issuecomment-903869569 for more details.
Workaround is to manually source a user's .profile first. This is not with Fish
@worldofgeese we've dug into this and a few related problems -- we think the best option is for Devbox to call and use the nix binaries directly, instead of expecting to find them in $PATH. We have some work on this and we're expecting it for the 0.2.1 milestone. Will update once it's finished!
@Lagoja safe to close?
| Owner Name | jetpack-io |
| Repo Name | devbox |
| Full Name | jetpack-io/devbox |
| Language | Go |
| Created Date | 2022-08-18 |
| Updated Date | 2023-03-31 |
| Star Count | 4960 |
| Watcher Count | 19 |
| Fork Count | 68 |
| Issue Count | 42 |
| Issue Title | Created Date | Updated Date |
|---|