Unable to install apps and virtualization not supported in virtualbox

I’m using TrueNAS Scale ElectricEel-24.10.0.1 in VirtualBox Version 7.0.22 r165102 (Qt5.15.2).
Unable to install apps and getting error “[EFAULT] Docker service is not running”.
In the apps menu, I also have this error: “Application(s) have failed to start:
[EFAULT] Default interface ‘enp0s8’ is not in active state”.

Not sure how to determine if the interface is inactive:
The interface ‘enp0s8’ is using bridge network and access to internet is fine.
Ping to google from shell is working fine.

Is it because nested virtualization is not supported thus I’m having issue? Virtualization do started not supported.

Any help is appreciate.

I still have no idea how to check why network interface is inactive. Try to restart the networking by using “systemctl restart networking” but apps still can’t be install.

While installing apps, the error docker not start lead me to enable and start docker service by using shell. After that, I’m getting another error “[Errno 2] No such file or directory: ‘/mnt/.ix-apps/app_configs’”.

Is there something that I miss out where the docker service doesn’t run itself. Though all this should be automated if I have setup properly.

Running Docker inside a VM can be tricky. I can’t offer direct help other than to suggest you ensure that you’ve enabled all the hypervisor extensions you need in VirtualBox for the virtualized BIOS and the VM settings, that you’ve enabled the nested hypervisor options for your host and VM in the VirtualBox configuration, and that you’ve installed the necessary guest helper packages from within the booted VM. The VirtualBox Guest packages are often required to give the guest access to some parts of the hardware.

If you’re on an x86_64 architecture you may also need to install the VirtualBox extensions package on the host, as without them some aspects of the host can’t be virtualized. These extensions aren’t available for ARM, though.

If none of that works, you may need to post some of your Docker or VirtualBox logs so someone else can offer you some better suggestions.

When running bridges in VMs it’s common to require the virtual interface to be configured in “promiscuous” mode in the vm configuration.