A new major release of the LXD Dashboard has just been released. There are a lot of changes to this release adding many more options to help manage LXD servers.
In this release the management of both container and virtual machines instances has been separated into two different pages. This has many added benefits to managing instances as containers and virtual machines use several different configuration properties. Also, users of legacy LXD versions (3.0.3) can now use the LXD Dashboard to manage their containers.
A new image catalog has been added to make it quick and easy to download LXD images. Users can still use the form to download images not listed in the catalog. This makes it simple to download either containers or virtual machines of your favorite Linux distributions.
Remote LXD hosts now have an option for an external IP address and port. This will provide the web socket connection a different address than what the LXD Dashboard uses to communicate to the server. If no external address and port are provided the web socket connection uses the default address and port.
Users can now manage the client.crt certificate that LXD uses to connect to LXD servers. This can be found in the settings page. If a user deletes the existing certificate, a new one will automatically be populated. This allows users to remove expired certificates as well as now changing the certificate used if the LXD Dashboard is cloned.
Both containers and virtual machines now display the CPU usage when viewing the specific instance.
Changes to the theme have added a fresh look with slightly darker pages.
I am trying to setup lxd dashboard for my lxd cluster. I am using archlinux lxc container for installation. I followed the installation guide for installing on lxc container, am able to get the registration page. There is no response after clicking register account. If I refresh the page it shows me a page with “Manage remote LXD servers with this open source LXD dashboard.For instructions on using the dashboard, visit https://lxdware.com.”
There are no errors in nginx and php-fpm logs. I understand that this was tested in an ubuntu container, but all of my linux installations are archlinux and would like to keep it alike.
It should work with Arch. It is most likely the Nginx webserver does not have permissions to create the sqlite database file or perhaps a php module is not loaded that is needed. I see your other comment in the 3.1.0 release post. I will reply to that comment with some things to try.