1.19.1

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

Please see Component versions for a list of updated components.

New features & improvements

  • The anbox-cloud-appliance status command now lists the version of the application that you are running.

  • The following snaps will be held from being automatically refreshed. They are refreshed only when the charms are upgraded.

    • ams

    • ams-node-controller

    • anbox-cloud-dashboard

    • anbox-stream-agent

    • anbox-stream-gateway

    • lxd

  • You can now see when an application or its version was created using the CreatedAt field listed when you run amc application show.

  • Android security updates for September 2023 (see Android Security Bulletin - September 2023 for more information).

  • The Android WebView has been updated to 116.0.5845.163.

  • Launching a stopped base container is no longer allowed.

Bugs fixed

  • LP 2031665 Appliance fails to refresh Grafana charm.

  • LP 2032172 Containers are stuck at Started status when using Android 13 images.

  • LP 2033372 Grafana installation fails because the GPG keys used previously were replaced with a new key. Starting this release, the key is updated automatically.

  • LP 2031463 Binder error causes service failure.

  • Session fails to start when using a GPU instance type with software video encoding.

  • Anbox Application Registry(AAR) charm fails when certificate is part of the relation multiple times.

  • The anbox-cloud-appliance.buginfo command displays empty outputs for juju status and juju config sections.

  • A disruption in the LXD node connection causes a crash in Anbox Management Service (AMS).

  • The model for the NETINT Quadra T1 U2 model was incorrectly encoded as QuadraT1-U2 instead of QuadraT1U.

  • Slowness in rendering due to old allocated buffers retaining the screen resolution even after the resolution changes.

  • Appliance fails to initialise on a machine with legacy BIOS.

  • I/O timeout issue on the supervisor channel caused by an incorrect write deadline for the WebSocket connection.

Upgrade instructions

See How to upgrade Anbox Cloud or How to upgrade the Anbox Cloud Appliance for instructions on how to update your Anbox Cloud deployment to the 1.19.1 release.