It's not you, it's me. My adventure with Vast.AI

[wolfman1360]

I don't run Linux from the command line because that is above my pay grade.

From the command line to start/stop BOINC use:

sudo service boinc-client stop
sudo service boinc-client start

The gui command that Z mentioned for your cc_config requires BOINC to be restarted for it to become active.

Okay, I must have been restarting the wrong part of Boinc. Upon further inspection Boinc isn't able to access the GPUs inside the Ubuntu docker image, despite vast claiming gpu drivers are installed. Can't remember the specific error message and apparently the log didn't save.
So maybe I need to try the Boinc docker image again regardless.
Not all that experienced in the terminal myself.
Further inquiries tell me that they are behind a firewall, but I should be able to use local port forwarding to theoretically bounce 31416 back to me and make it available using PuTTY? Have never done that before.

Sometimes I'm too stubborn for my own good...