Possibly, but if the server has never had a ./launcher cleanup then it could be old images jamming the place up. It seems like it was created from a one-click install, so may have skipped the server maintenance section of the standard install.
I’d quite like to see the output of docker images to confirm, but if there’s an orphaned one in there that’s prime for removal, and that frees up enough space to get it back online and on the right maintenance track, that should give a clearer picture.
But you’re right, resizing may be simpler.