I’ve been using VirtualBox for a year now and I’m getting pretty ticked every time I have to start a new Ubuntu VM. I speed more time going to root shell prompt to add myself to sudoers file, add myself to groups, the addons, shared folder and storage not mounting right away….. etc etc.
I’m sure I might be not using VirtualBox to its full potential to avoid long setup times but I feel like I shouldn’t have to deal with this. It should act is it being installed on a bare metal machine. Is there a more modern approach? Something more streamlined?
FYI I’m learning containers and miniKube so I’m not jumping in the deep end yet.

I’ve been using VirtualBox for a year now and I’m getting pretty ticked every time I have to start a new Ubuntu VM. I speed more time going to root shell prompt to add myself to sudoers file, add myself to groups, the addons, shared folder and storage not mounting right away….. etc etc.
I’m sure I might be not using VirtualBox to its full potential to avoid long setup times but I feel like I shouldn’t have to deal with this. It should act is it being installed on a bare metal machine. Is there a more modern approach? Something more streamlined?
FYI I’m learning containers and miniKube so I’m not jumping in the deep end yet.

Some combination of Ansible and cloud-init is probably what you're looking for.

I’ve been using VirtualBox for a year now and I’m getting pretty ticked every time I have to start a new Ubuntu VM. I speed more time going to root shell prompt to add myself to sudoers file, add myself to groups, the addons, shared folder and storage not mounting right away….. etc etc.
I’m sure I might be not using VirtualBox to its full potential to avoid long setup times but I feel like I shouldn’t have to deal with this. It should act is it being installed on a bare metal machine. Is there a more modern approach? Something more streamlined?
FYI I’m learning containers and miniKube so I’m not jumping in the deep end yet.

I’ve been using VirtualBox for a year now and I’m getting pretty ticked every time I have to start a new Ubuntu VM. I speed more time going to root shell prompt to add myself to sudoers file, add myself to groups, the addons, shared folder and storage not mounting right away….. etc etc.
I’m sure I might be not using VirtualBox to its full potential to avoid long setup times but I feel like I shouldn’t have to deal with this. It should act is it being installed on a bare metal machine. Is there a more modern approach? Something more streamlined?
FYI I’m learning containers and miniKube so I’m not jumping in the deep end yet.

I’ve been using VirtualBox for a year now and I’m getting pretty ticked every time I have to start a new Ubuntu VM. I speed more time going to root shell prompt to add myself to sudoers file, add myself to groups, the addons, shared folder and storage not mounting right away….. etc etc.
I’m sure I might be not using VirtualBox to its full potential to avoid long setup times but I feel like I shouldn’t have to deal with this. It should act is it being installed on a bare metal machine. Is there a more modern approach? Something more streamlined?
FYI I’m learning containers and miniKube so I’m not jumping in the deep end yet.

I’ve been using VirtualBox for a year now and I’m getting pretty ticked every time I have to start a new Ubuntu VM. I speed more time going to root shell prompt to add myself to sudoers file, add myself to groups, the addons, shared folder and storage not mounting right away….. etc etc.
I’m sure I might be not using VirtualBox to its full potential to avoid long setup times but I feel like I shouldn’t have to deal with this. It should act is it being installed on a bare metal machine. Is there a more modern approach? Something more streamlined?
FYI I’m learning containers and miniKube so I’m not jumping in the deep end yet.

I'd take a look at packer and ansible. Packer can be used to prepare a new base image for your VMs. And ansible can be used to automate the provisioning of a VM once it's booted.

Some good advice already in this thread.

Also worth considering QEMU as an alternative to VirtualBox. The Virt-manager tool is decent way of managing machines, and it's relatively straight forward to create a base machine if you're duplicating it. Virtualbox is perhaps initially more user friendly for absolute beginners, but once you have any familiarity with virtualization I'd suggest QEMU offers much more.

Also I find integration between the guest and the host linux system is generally more straight forward. Most linux systems already ship with samba and other relevant tools QEMU uses to interact between host and guest. There isn't a need to faff around with the guest-additions stuff. Plus KVM virtual machines can run with near native performance.

There's many ways to do this. Saving the disk state is one, I believe that's what the other person suggested - essentially stores the disk as an image which then you use for future vms as your jumping off point. This is also essentially how workstations are deployed at companies. (Essentially being the key word). Cloud providers have different names for this too, in AWS this is called their AMI.

Another option is Ansible, which essentially handles deploying a VM by running your scripts for you. I haven't played too much with this, and I doubt it works with VirtualBox, but it's something you may want to look into, it would definitely uplevel your skills.

Thirdly is dependent on what you actually use your VM for, you haven't given your use cases but this is one of the reasons containerization became such a thing - because when running an app we mostly don't care about the underlying system. It may be worth it to learn about docker.

There is also Vagrant which lets you specify VM specs, but also lets you install software in the VMs automatically. It also works for other VM software then just Virtualbox.

Simple method is just keep a ready to go VM and clone it.

I’m playing with a multicast data delivery software I’m building. Doing tests from a sever (VM) to 20+ clients and/or other server (VMs). All running through a Open5GS gNodeB (5G network core). Also testing out potential software to be a docker image. I’m slowly converting to containers but I might just need to make the leap.

Thank you!

I’ve been using VirtualBox for a year now and I’m getting pretty ticked every time I have to start a new Ubuntu VM. I speed more time going to root shell prompt to add myself to sudoers file, add myself to groups, the addons, shared folder and storage not mounting right away….. etc etc.
I’m sure I might be not using VirtualBox to its full potential to avoid long setup times but I feel like I shouldn’t have to deal with this. It should act is it being installed on a bare metal machine. Is there a more modern approach? Something more streamlined?
FYI I’m learning containers and miniKube so I’m not jumping in the deep end yet.

I’ve been using VirtualBox for a year now and I’m getting pretty ticked every time I have to start a new Ubuntu VM. I speed more time going to root shell prompt to add myself to sudoers file, add myself to groups, the addons, shared folder and storage not mounting right away….. etc etc.
I’m sure I might be not using VirtualBox to its full potential to avoid long setup times but I feel like I shouldn’t have to deal with this. It should act is it being installed on a bare metal machine. Is there a more modern approach? Something more streamlined?
FYI I’m learning containers and miniKube so I’m not jumping in the deep end yet.

NP! That's how I do it on proxmox, I'll start the VM every so often and update it. Only takes a few seconds to clone so it's nice and quick to do.