Replies: 3 comments
|
Actually, it looks like I can work around this fairly elegantly using |
0 replies
|
Hmm... I've tried to remove the need for having the MISE_CEILING_PATHS env var set by tweaking the miserc, but that doesn't seem to work. I tried this: and I've also tried: But I still see: |
0 replies
|
For now, this is what I've settled on, in my # If we're not on macOS,
# and we have a /Users directory (likely mounted via OrbStack from a host macOS),
# then configure mise to ignore /Users/*.
# https://github.com/jdx/mise/discussions/8433
if [[ ${OSTYPE} != darwin* ]] && [[ -d /Users ]]; then
export MISE_CEILING_PATHS=${(j.:.)$(echo /Users/*(/N))}
fi |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
OrbStack allows for running Docker containers and Linux "machines" on macOS. One of the nice features is that many of the host's top level directories are mounted into the guest Linux VM, including
/Users. This allows for you to be in a directory like~/src/my-projectfrom a regular macOS shell, run something likeorb -m ubuntuto drop into a shell running at/Users/${USER}/src/my-projectwithin the guest, and transparently read/write files in both directions (this user directory shouldn't be mistaken for the guest user's home directory, which would be somethiing like/home/${USER}).Here's the problem, though: within the guest,
misewill find and use the/Users/${USER}/.config/mise/config.toml, which will override what should be the default user config at/home/${USER}/.config/mise/config.toml. This confuses things, wheremisewill do things like see yourmise use -g node@16and find that node@16 is already set, and thus not install/reshim/etc as needed within the guest.I can see two solutions:
misebinary is running on (i.e. compiled for) Linux, and the current working directory is under/Users, assume that the scenario is as I describe here, and preclude/reject files like/Users/${USER}/.config/mise/config.tomlfrom the search path.Would either of these solutions be accepted? It would make usage much more straightforward if
misewould not pick up the config file intended as user-level config for the host OS's user, when running within a guest VM.All reactions