> Separately i'm failing to get even as far as the bug description gets
> as i get failures on missing newuidmap binary and what not:

The log looks exactly like what you should see. The error about missing
newuidmap/newgidmap is expected as LXD writes the uidmap for the
container directly and doesn't use the two tools to do that. The first
two errors is what we look for:

lxc evident-oyster 20220509154201.271 ERROR conf - conf.c:run_buffer:321 - 
Script exited with status 1
lxc evident-oyster 20220509154201.271 ERROR conf - conf.c:lxc_setup:4400 - 
Failed to run mount hooks

Any error following after this is just a consequence of the start
process failing here.

If you have the NVIDIA drivers installed, as Stephane mentions, and also
set

$ lxc config set c0 raw.lxc lxc.log.level=0

you will get the error as given in the description. If you don't enable
trace logging you will always remain with just

lxc evident-oyster 20220509154201.271 ERROR conf - conf.c:lxc_setup:4400
- Failed to run mount hooks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971978

Title:
  Driver binaries fail to load on arm64 through LXD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1971978/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to