ArtixWSL icon indicating copy to clipboard operation
ArtixWSL copied to clipboard

How to properly start the supervision tree?

Open tleydxdy opened this issue 4 years ago • 1 comments

e.g. for the suite66 system, how to I start the tree so things work properly? I would imagine that may things in the boot tree would not work under WSL2

tleydxdy avatar Oct 20 '21 18:10 tleydxdy

Sorry for taking so long to reply.

I haven't thoroughly tested it myself yet, but I think running services on suite66 should be done in a similar way to runit (check runsvdir.ps1 example script): you should not run boot tree and use a separate tree for services under WSL (1 or 2 should not matter here)

Something like this should do the trick:

# On WSL it refuses to run under /run, so let's run it elsewhere
mkdir -p /root/66
mkdir -p /run/66
mount --bind /root/66 /run/66

66-tree -n wsl
66-enable -t wsl nginx
66-scandir create
66-scanctl start

# In separate terminal:
66-all -t wsl up

In a more realistic scenario, scanctl should be supervised by something else on Windows itself.

hdk5 avatar Nov 03 '21 19:11 hdk5