OS Name: Ubuntu Minimal (Docker) / arm64v8
Product Name/Version: AMP version 220.127.116.11 (Lapetus), built 27/04/2020 16:38, MinecraftModule version 18.104.22.168
I am trying to run AMP inside Docker on an AWS ECS Cluster of m6g instance(s) (arm64v8 processor architecture).
When attempting to launch the Minecraft instance with
ampinstmgr StartInstance MinecraftInstance, I am seeing the following error:
[Core Error] : Couldn't activate: The URI prefix is not recognized. which I believe is causing failure in attempting to start the instance.
I also note some some warnings from the Minecraft module:
[Minecraft Warning] : Unable to get Spigot version data from https://hub.spigotmc.org/versions/: Response status code does not indicate success: 403 (Forbidden).
[Minecraft Warning] : Failed to get latest forge version data from http://files.minecraftforge.net/maven/net/minecraftforge/forge/maven-metadata.xml. An exception occurred during a WebClient request.
Full Logs: https://pastebin.com/fVsMbhmd
I am able to successfully call these URLs with a 200 response code within the docker container, so this may indicate a problem.
Steps to reproduce:
I've been building arm64v8 docker images on an x86-64 system with
docker buildxon Ubuntu according to these instructions: https://community.arm.com/developer/tools-software/tools/b/tools-software-ides-blog/posts/getting-started-with-docker-for-arm-on-linux
docker buildxas the default builder: https://docs.docker.com/buildx/working-with-buildx/#set-buildx-as-the-default-builder
Dockerfile: https://pastebin.com/Pij4VKD1 (shell scripts can be ignored for reproducing)
docker buildx build --platform linux/arm64 --load --tag aws-minecraft:latest
docker run -it --entrypoint /bin/bash aws-minecraft:latest(this will run locally on an x86 system, but I was seeing the same issue on a real ARM machine (which I've included the logs for above)
ampinstmgr CreateInstance Minecraft MinecraftInstance 0.0.0.0 8080 LICENSE_KEY admin changeme123(with real
ampinstmgr StartInstance MinecraftInstance(instance fails to start)
ampinstmgr LastLogs MinecraftInstance(note the error in logs)
Actions taken to resolve so far:
I've run into a number of issues so far, most notably was an issue with
mono for the default version included in the Ubuntu base docker image. I manually install the latest version of
mono in the
Dockerfile which resolved that issue.
I have verified that I can call the endpoints listing in warnings successfully (200) inside the container with