AMP Minecraft Instance cannot run Windows Subsystem for Linux when trying to update Spigot server.

  • 42 Views
  • Last Post 25 June 2020
Fawenah posted this 24 June 2020

Hello.

I am having some issues that AMP is not finding WSL when I'm trying to run an Update for a Minecraft server instance with a Spigot target.

OS Name/Version:
Windows 10 Pro
Version 1909
Build 18363.900

Product Name/Version:
AMP Release "Lapetus"
v1.9.9.10, built 23/06/2020 23:18
Minecraft Module

Problem Description:
Cannot utilize the "update" function on the Minecraft module, as it fails to find Windows Subsystem for Linux (WSL), even though it is installed.
Starting a command prompt on the instance from AMP Instance Manager, and running "wsl" starts my installed WSL distrobution "Ubuntu 20.04 LTS (GNU/Linux 4.4.0-18362-Microsoft x86_64)". So it exists, is runnable from the instance command prompt. I can manually perform the Spigot build on my PC.

The issue seems to be that AMP can't find / start WSL. I assume there's maybe some permission / user configuration I need to do.

Steps to reproduce:

  • Start AMP Instance and a Minecraft module instance
  • Open up the panel in Chrome, and "manage" the Minecraft instance
  • Click "Update", with "Spigot", as Server Type, and "Stable" as the selected release stream.

Actions taken to resolve so far:
- Updated AMP, and WSL - Test built Spigot manually from windows command prompt, and within WSL (works) - Started WSL via the AMP instance command prompt (works)

Notes:
Selecting the "Official" server type, and updating appears to be working fine, but I assume that does not try to use WSL.
AMP and the Minecraft instance is running as a service. I've tried running the Minecraft Instance not as a service with the same issue.

I appreciate any help I can get.

Console Log on the Minecraft Instance:

[22:30:03] [GSMyAdmin:admin Activity] : Updating the application.
[22:30:04] [Minecraft:admin Info] : Selected release stream is Stable...
W i n d o w s   S u b s y s t e m   f o r   L i n u x   h a s   n o   i n s t a l l e d   d i s t r i b u t i o n s . 


 D i s t r i b u t i o n s   c a n   b e   i n s t a l l e d   b y   v i s i t i n g   t h e   M i c r o s o f t   S t o r e : 


 h t t p s : / / a k a . m s / w s l s t o r e

Mike posted this 25 June 2020

You shouldn't be using WSL with AMP. This is caused by not having the correct git for Windows installation as AMP is expecting to use the utilities from that to run buildtools.

Close