You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your Windows build number: (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.17763.437]
ray@LAPTOP-JNA8O7S4:/mnt/c/Users/rayj0$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
ray@LAPTOP-JNA8O7S4:/mnt/c/Users/rayj0$
What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)
ray@LAPTOP-JNA8O7S4:/mnt/c/Users/rayj0$ sudo service lxd start
[sudo] password for ray:
Starting Container hypervisor based on LXC: lxd.
Error: LXD still not running after 600s timeout (Get http://unix.socket/1.0: dial unix /var/lib/lxd/unix.socket: connect: no such file or directory)
ray@LAPTOP-JNA8O7S4:/mnt/c/Users/rayj0$
What's wrong / what should be happening instead:
LXD should be running. It does not start up?
Strace of the failing command, if applicable: (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here).
For WSL launch issues, please collect detailed logs.
The WSL bionic dode not have the logman command
Would running Ubuntu 16.04 be the better choice?
This can be a landing zone I guess, but the ask is spiritually dupe a Venn diagram combination of #2374#2291#994, and the ever popular #412. No strace(1) log provided natch. If you had, you would hit the first of a few blockers. As a starting point you can upvote UserVoice here, here, here, here plus some lesser others not worth citing.
I would really like to run LXD on WSL. Please don't suggest HyperV or vBox. I am working on an application that uses LXD on my VPS under Ubuntu 16.04 and I can at least run LXD and create containers. On WSL, I can't do squat as LXD will not start because of that systemd issue! Please fix!
Please fill out the below information:
ver
at a Windows Command Prompt)Microsoft Windows [Version 10.0.17763.437]
ray@LAPTOP-JNA8O7S4:/mnt/c/Users/rayj0$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
ray@LAPTOP-JNA8O7S4:/mnt/c/Users/rayj0$
ray@LAPTOP-JNA8O7S4:/mnt/c/Users/rayj0$ sudo service lxd start
[sudo] password for ray:
Starting Container hypervisor based on LXC: lxd.
Error: LXD still not running after 600s timeout (Get http://unix.socket/1.0: dial unix /var/lib/lxd/unix.socket: connect: no such file or directory)
ray@LAPTOP-JNA8O7S4:/mnt/c/Users/rayj0$
What's wrong / what should be happening instead:
LXD should be running. It does not start up?
Strace of the failing command, if applicable: (If
some_command
is failing, then runstrace -o some_command.strace -f some_command some_args
, and link the contents ofsome_command.strace
in a gist here).For WSL launch issues, please collect detailed logs.
The WSL bionic dode not have the logman command
Would running Ubuntu 16.04 be the better choice?
See our contributing instructions for assistance.
The text was updated successfully, but these errors were encountered: