04 March 2019
I just created a new Minecraft instance with Docker support inside ADS. I checked in docker and it shows the container created and running, but when I try to hit "start instance" I get the same error as before.
However, since I can see the container is running now, which it wasn't before today, I waited, refresh, and noticed the instance now showed as running.
So the error it gave wasn't accurate just now. "Task Starting Instance (Starting Docker-Test (Minecraft02)...) failed:"
Inside the new instance there is an error "[15:59:30] [Minecraft Warning] ???: Failed to get latest forge version data. The remote server returned an error: (404) Not Found."
But otherwise the docker instance appears to be working. From the logs and what happened, it looks to me that simply creating the docker instance also auto-runs the container, instead of waiting for me to hit start.