Skip to content
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

Support for Windows 10 #1115

Open
steskalja opened this issue Apr 24, 2019 · 16 comments

Comments

@steskalja
Copy link

@steskalja steskalja commented Apr 24, 2019

Has there been any exploration in to porting this to Windows?

@TheBrokenRail

This comment has been minimized.

Copy link

@TheBrokenRail TheBrokenRail commented Apr 28, 2019

As this use the Linux kernel, this would likely only work on WSL.

@sheldonmaschmeyer

This comment has been minimized.

Copy link

@sheldonmaschmeyer sheldonmaschmeyer commented May 6, 2019

Beyond a VM, you might be able to use the UNIX subsystem for Windows 10, based on Ubuntu Linux. It is more akin to a compatibility layer. To run graphical programs, you need to get the X server working , instructions linked here: https://www.howtogeek.com/261575/how-to-run-graphical-linux-desktop-applications-from-windows-10s-bash-shell/

anbox uses Snapcraft which is Linux specific. Right now they are in Beta/Alpha stage so, Windows would be a long time from now....using the UNIX subsystem is untried, tested. If you get it to work with it, I'd like to know.

@benjimaestro

This comment has been minimized.

Copy link

@benjimaestro benjimaestro commented May 14, 2019

This won't work directly on Windows 10, you'll have to wait for WSL 2 to release in June/July to see if it'll work there.

@benjimaestro

This comment has been minimized.

Copy link

@benjimaestro benjimaestro commented Jun 14, 2019

So now that WSL 2 has released, I've given it a try. There's no systemd present on WSL 2, so Anbox will still not work on Windows 10 - you either have to wait more for MS to add support for it, or for another solution to come by.

@dlee13

This comment has been minimized.

Copy link

@dlee13 dlee13 commented Jun 23, 2019

I'm not at all familiar with WSL 2 and how anbox works or what anbox needs from systemd, but this discussion seems relevant.
microsoft/WSL#994 (comment)

Have you attempted this method of running systemd?
https://github.com/arkane-systems/genie

@WSLUser

This comment has been minimized.

Copy link

@WSLUser WSLUser commented Jun 24, 2019

I would love to see this up and running on #WSL2 once the bugs in genie get fixed.

@cerebrate

This comment has been minimized.

Copy link

@cerebrate cerebrate commented Jul 1, 2019

Unless there's some highly specific dependency on the shell process being a n-child of pid 1 (i.e., the first in the genie bugs list, which may not be soluble unless there's a way to reparent processes that I'm missing), there shouldn't be any blockers in genie for this.

That said, the blocker we do have right now is that there isn't squashfs support in the current WSL 2 kernel (ref here: microsoft/WSL#4123 ) which is a snapd dependency, although as you'll see, that's fix-inbound. Once the new version's out, I expect snaps to work just fine, and I suspect also anbox.

@cerebrate

This comment has been minimized.

Copy link

@cerebrate cerebrate commented Jul 2, 2019

So, I figured out a way to use a custom kernel with WSL 2 (see here: https://gist.github.com/cerebrate/d40c89d3fa89594e1b1538b2ce9d2720 ), and thus got squashfs, snaps, etc. working, and so I figured between that and genie I'd have a shot at getting this working. Sadly, I run into issues when trying to install the anbox kernel modules, per attached.

make.log

I can't say that I'm all that familiar with dkms et. al., but if anyone with more familiarity and a moment to help figure this out has any ideas as to causes and cures, do please get in touch.

@hacker1024

This comment has been minimized.

Copy link

@hacker1024 hacker1024 commented Jul 16, 2019

@cerebrate
It looks like header files are missing needed to built the module. Have you installed the headers for your custom kernel as well as the kernel itself?

@cerebrate

This comment has been minimized.

Copy link

@cerebrate cerebrate commented Aug 4, 2019

So, after some distraction, I've fixed the problems with my custom kernel build and got the modules up and running, at which point the anbox snap installs, and the anbox service appears to be running without complaint per systemctl status, etc.

Having a few issues at this point that I'm still poking at, which I shall give details on in my next post a bit later tonight. Meanwhile, though, I'm using

anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity

as my test just-make-it-do-something command. Is that a good choice, or is there something else you might recommend for the most basic test of anbox functionality?

@cerebrate

This comment has been minimized.

Copy link

@cerebrate cerebrate commented Aug 4, 2019

Okay. So what I'm seeing now when I run

anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity is a window (containing the Android logo and 'Starting...') appearing briefly and then closing, and this message:

[ 2019-08-04 06:20:56] [daemon.cpp:61@Run] Failed to retrieve ready property from application manager
 [1]    16376 exit 1     anbox launch --package=org.anbox.appmgr

journalctl shows the following log entries:

Aug 04 01:24:27 athena-wsl anbox[17116]: Failed to start container: Failed to start container: Failed to start container
Aug 04 01:24:27 athena-wsl anbox[17116]: Lost connection to container manager, terminating.                                                                 
Aug 04 01:24:28 athena-wsl anbox[17116]: Container is not running                                                                                           
Aug 04 01:24:28 athena-wsl anbox[17116]: Lost connection to container manager, terminating. 
@cerebrate

This comment has been minimized.

Copy link

@cerebrate cerebrate commented Aug 4, 2019

(This could be #790 , if #790 is still a thing.)

@cerebrate

This comment has been minimized.

Copy link

@cerebrate cerebrate commented Aug 4, 2019

Herewith full diagnostics of the error in question:

anbox-system-diagnostics-2019-08-04.zip

@stale

This comment has been minimized.

Copy link

@stale stale bot commented Dec 2, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the decaying label Dec 2, 2019
@aXe1

This comment has been minimized.

Copy link

@aXe1 aXe1 commented Dec 3, 2019

IMHO it is still more than relevant.

@stale stale bot removed the decaying label Dec 3, 2019
@cyb3rm4n

This comment has been minimized.

Copy link

@cyb3rm4n cyb3rm4n commented Dec 4, 2019

any info about WSL support?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
10 participants
You can’t perform that action at this time.