Native Windows Build

[dchw]

We have a new, experimental release that runs natively on Windows.

It can only run and work with Linux containers. It does not include support for Windows containers. Windows container support is a larger issue that includes work upstream.

This is a tracking issue to be kept open until it is fully released. If you encounter any issues, ping me here!

Current known issues:

• FROM DOCKERFILE does not work
• No tab completions
• Ongoing time reports may be off when WSL/HyperV dates desync due to hibernation
• Integration with the desktop.exe credential store

This issue is part of #544

[Jaykul]

It's hard for me to believe 2023 is almost over, and there's no comments in here...

Is it known already that --interactive does not work?

earthly debugger | failed to start pty: failed to write data to conn: 
write unix @->/tmp/.buildkit-socketforward2688254145/sock: write: broken pipe

[aronchick]

We need to build on windows - what's the best practice here?

[Jaykul]

If you mean build in linux containers on Windows, you'll be fine. Use the native Windows' executable.

The --interactive (or -i) switch still doesn't work in the "Native Windows" build, because it still doesn't support ConPTY....

But since you'll have WSL installed anyway for docker, you can install earthly in your ubuntu (or whatever) distro, and literally just run: wsl earthly -i +test and it will work ;-)

[Jaykul]

It looks like LOCALLY doesn't work either, whether you try to COPY or RUN you get an error like:

failed: error calling LocalhostExec: rpc error: code = Unknown desc = mkdir /C:: The filename, directory name, or volume label syntax is incorrect.

[Jaykul]

LOCALLY still doesn't work at all on Windows (see #1865)