Ah, my mistake, ok, that makes sense.
Did that, getting a
e":"No such container: ef1fab5b8f0a"}
Stopped and restarted a few times, just continues 'normally' after - does it delete the fx.tar after it updates?
Yes - the very first time I installed, it did look like it opened up a WebConsole page (with port 9016), but it was blank - then I deleted everything (docker container, folder, verified it was gone, even deleted the entire docker.img), and started from scratch again but for whatever reason, it tries to load up with port 8080.
This server that I'm testing on has just been spun up specifically for FiveM - just want to get the feel of it, then once I do, I'll start to put this on my production server (my production server isn't at my house, so I rather quickly do things locally first). So there's nothing else on this server, except FiveM (then I put on Krusader after to help delete things).
Does it go through those loads every time?
I thought something was wrong with this loading, but wasn't sure if it was just that simple...