Anbox Cloud 1.21.0 has been released

Anbox Cloud Announcements
1

Introduction

The Anbox Cloud team is pleased to announce the release of Anbox Cloud 1.21.0.

Please see component versions for a list of updated components.

New features & improvements

The 1.21.0 release of Anbox Cloud brings the following features and improvements:

Core stack improvements

  • Android Automotive (AAOS) images with experimental VHAL support are available. See Provided images for more details.

  • Initial support for installing Anbox Cloud Appliance on Ubuntu 24.04.

  • Production support for Vulkan on NVIDIA GPUs is available but remains opt-in. Support must be explicitly enabled and set up. For instructions on enabling the VirGL rendering path for Vulkan support, see How to enable VirGL.

    This release also provides Renderdoc support for debugging purposes. See Graphics debugging with renderdoc for more information.

  • The NVIDIA UDA driver variant with version 545 or later can be installed with the Anbox Cloud Appliance by using the nvidia-driver-series and use-nvidia-uda-driver flags with the anbox-cloud-appliance init command.

  • GL Async swap support is disabled by default. See GL Async swap support for more information.

  • In the AMS HTTP API, /1.0 endpoint exposes the cluster ID and name to enable identifying a subcluster.

  • The Anbox Cloud NFS operator charm now supports mounting EFS file system on AWS when you require Transport Layer Security (TLS). With an EFS file system, you can configure the charm with the following parameters:

    • mount_type set to efs
    • nfs_extra_options set to tls

  • The Anbox Application Registry(AAR) can make use of Identity and Access Management(IAM) roles applied to an AWS instance using instance profiles. This relieves you from having to configure an access key/secret for instances. For information on how to use an IAM role in AAR, see how to deploy AAR.

  • The NATS charm is switched from its older version to a newer version on Charmhub. This would require that you switch to the new charm source. For more information, see How to upgrade Anbox Cloud.

Dashboard improvements

The following improvements are available in the Anbox Cloud dashboard for this release:

  • Launching an instance independent of a session is now possible using the Anbox Cloud dashboard. This is especially useful for situations where you want to create an instance but do not want to stream anything. To do this, select the Create Instance button on the Instances view, provide the information required for instance creation and select Create and Start.
  • Support multiple subclusters from the dashboard for large scale deployments.
  • Client side upscaling is now available as an experimental feature.You can now add upscaling as a query parameter to your session URL. For example, http://<ip_address_of_instance>/sessions/<session_ID>?upscaling=true.
  • Experimental support for managing the Vehicle Hardware Abstraction Layer (VHAL) properties for AAOS images.
  • Enhancements for improved responsiveness, error handling and messages
  • Updated Python and Javascript dependencies.

Other

Removed functionality

  • Clustering support (which existed as an experimental feature) for Anbox Cloud Appliance is removed.
  • The deprecated Android 11 images are now unsupported and hence removed.

Known issues

  • LP 2053106 In the Anbox Cloud dashboard, selecting the Download all button to download all logs from an instance in Error state displays a Page not found (404) error.

Bug fixes

  • Invalid session error When streaming an audio-only WebRTC session.
  • Initialising Anbox Cloud Appliance as root user causes a missing AMC client cert error.
  • LP 2049734 INSTANCE_TYPE is set to regular instead of base during the runtime of the post-stop hook of an addon.
  • When using the web dashboard for application creation, changing the container/VM radio button from one option to another causes a spurious error about the image not being of type string. This error occurs only when there is no default container image present.
  • When using the AMS HTTP API, the API response for GET /1.0/instances does not properly return information for the fields config and resources.
  • Video decoder is not considered inactive when initialisation fails.
  • Concurrent stop operations on the same instance occurs due to mixed responsibilities in two internal AMS components.

Upgrade instructions

See Upgrade Anbox Cloud or Upgrade the Anbox Cloud Appliance for instructions on how to update your Anbox Cloud deployment to the 1.21.0 release.

7 Likes