Once you’ve created an S9PK that you’d like to test, inside embassyOS click System in the sidebar, and then click Sideload Service under Manage. When I finish networking my VM, I’ll write that up so that sideloading is possible. If anyone else has a writeup for this, I’ll include it.
This is awesome, thank you so much for this guide, Spencer!
One thing I would mention, this is a perfect setup but there’s a quirk, if you happen to cancel out of the install, for some reason, it won’t boot the installer again until you do this:
Right click the VM and go to Open
Click the light bulb to configure the VM
Go to IDE CDROM 1
Under Source Path, click Browse
Under final, select eos-0.3.x-xxxxxxxx_amd64.iso, and click “Choose Volume”
Go to Boot Options
Enable IDE CDROM 1 and position it above IDE Disk 1
Now you can happily boot the installer even if you accidentally canceled out of it the first time, or want to reinstall. Just remember to also demote IDE CDROM 1 from the boot order after your initial setup.
You should be able to edit posts, and it shows that you have made edits to posts previously. I’m trying to see if there’s a rate limit, but not seeing anything on my end. Are you getting an error or message regarding this? Maybe we should move to a chat
The other day I found a message board that said (I believe) that by default Discourse allows editing only for 5 hours after the original post. (Presumably to cut down on people going in to popular posts and adding spam after the fact.)
Having the complete node with embassyOS run as a virtual machine is a cool idea. I would like to do this for my full node implementation. It would keep the host machine usefull for some other tasks.
I do have some questions and concerns mostly on the networking part. Do I need to bridge the virtual machine to make it connect to the internet and do its job as a full node? If so, I could use the KVM bridge or the passthrough (less isolated) what would you suggest?
A very different way could be to have the node run in a docker container, what would be the pro’s and cons of that? I have almost zero know-how on docker so it may be very bad idea.
We would recommend using standalone hardware for your server, as it is intended to run 24/7/365. If you don’t have that option, or if you’re just doing some testing, then a VM is a great option.
You may need to bridge the network.
You can think of StartOS as an Operating System that orchestrates containers. Currently all services run in docker containers (although the system is modular and in future will be able to use other containerization options as well). So if you use this, you actually will be running docker, and in a much simpler way than having to learn it all yourself.
At first i thought to set-up the mini-pc for being a full node only. Along the way it came to mind it migh tbe strong enough to have a dual task as it has 6 cores, 16 GB of RAM and 2 TB nvme SSD. But you are right it is wiser to have it commit 100% to being a full node.
I do wonder if it would be possible to do KVM tier-1 virtualization and have the best of both options (all ubuntu stuff and usb-ports and extra dives working) and a stable full node that is very close to a
bare -iron install?
I went for the direct install on iron in the end. It may be a bit wastefull of resources but at least it helps with debugging if there are issues with the set-up.; not having to deal with the extra complexity of a virtual machine.