-
Notifications
You must be signed in to change notification settings - Fork 796
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A future proof way to determine we are inside bash on windows. #2479
Comments
@vStone It's currently unknown what the end-state for hardware implementation will be. WSL may even end up with direct block-level access to unmounted Windows devices, or direct hardware access for graphics or CUDA for example, so it's not safe to just declare WSL as virtual. As Ken has mentioned before, it would be really helpful for the team to give us a roadmap, but at the moment, management has decided to to keep the roadmap private (and therefore flexible). Certain workarounds for WSL bugs/unimplemented syscalls should not be candidates for addition to compatibility fixes in Linux projects. They should be reported on this github repo instead and considered temporary. If the problems are more fundamental (mainly revolving around missing kernel modules that the WSL team doesn't plan to replace with their own implementations), then designing around WSL limitations could make sense. |
Duplicate of #423. |
Facter should determine correctly we are running inside a vm of some sort.
I'm looking for a future proof way to determine we are running inside a vm on windows so I can make the patch upstream to puppetlabs for fixing this.
This is the current implementation in facter:
Upstream ticket: https://tickets.puppetlabs.com/browse/FACT-1748
The text was updated successfully, but these errors were encountered: