Application Fails to initialise with error on clean install of anbox cloud appliance

[John Smith]

Failed to start device "anbox_sw_sync": The required device path doesn't exist and the major and minor settings are not specified

Name ams-cg683r9q3nog22a943ng
Container ID cg683r9q3nog22a943ng
App name testapp
App ID cg683r9q3nog22a943n0
App Version 0
Created At 11 Mar 2023, 11:28:13 pm
Address
Public Address
Status error
Error Message Failed to start device "anbox_sw_sync": The required device path doesn't exist and the major and minor settings are not specified
Type base
Tags

[Simon Fels (morphis)]

Hey John,

that looks like the `anbox_sync` kernel module isn't loaded. The anbox-modules-dkms-* package puts a /etc/modules-load.d/anbox.conf in place which should load the module by default. That this doesn't work seems to indicate that either building the dkms package failed or you might run with secure boot and haven't registered a mok key.

Can you provide us

$ sudo anbox-cloud-appliance.buginfo

Thanks!

[Launchpad Janitor (janitor)]

[Expired for Anbox Cloud because there has been no activity for 60 days.]

[Roberto Imai (roberto-imai)]

I am getting the same error.
I installed ubuntu server on a fresh machine and followed the tutorial to get Anbox up and running.
Everything went well until I tried to add an application, which fails and the container has this error message: "Failed to start device "anbox_sw_sync": The required device path doesn't exist and the major and minor settings are not specified"
I attached the log requested above.

[Roberto Imai (roberto-imai)]

I was able to get by disabling Secure Boot on shim.
https://wiki.ubuntu.com/UEFI/SecureBoot/DKMS

[Simon Fels (morphis)]

Thanks Roberto! Yes, disabling secure boot is required unless you have a MOK in place. See https://wiki.ubuntu.com/UEFI/SecureBoot

We will add a check into the appliance to check for this in future releases.