The Anbox Cloud team is pleased to announce the release of Anbox Cloud 1.15.0.
Please see component versions for a list of updated components.
New features & improvements
- All snaps are now based on the
core20snap, which removes the need to have older base snaps (for example,
core18) installed on newer Ubuntu versions.
- AMS now provides support for a development mode for containers. This development mode mainly turns off status updates for the Anbox runtime inside a container, which usually cause AMS to stop the container.
- TLS 1.3 is now enforced by default. This means that if you’re running older images (< 1.15), they will fail to talk to AMS. You can temporarily enable TLS 1.2 support in AMS again by setting the
force_tls12configuration option of the AMS charm.
- With the new
cpu.limit_modeconfiguration, the default strategy that AMS uses to assign CPU time to a container via the Linux kernel scheduler can be changed to use CPU core pinning instead. See the documentation for more details and the caveats that each mode has.
- If AMS is behind a load balancer, it can now be configured with the address of the load balancer via the
load_balancer.urlconfiguration item. This configuration will instruct containers to go through the load balancer instead of reaching out to the particular AMS instance that launched them.
- The WebRTC streamer configuration can now be customised. Currently, only the minimum and the maximum bitrate can be configured, in addition to some options specific to NVIDIA NvEnc.
- Tracing support in Anbox now includes support for tracing the WebRTC stack as well.
- A new HTTP
/1.0/platformAPI allows runtime configuration of the currently loaded platform. For WebRTC, you can now enable RTP trace collection and retrieve information about the current status of the streamer.
- Anbox now uses the recently released LXC 5.0.
- The WebRTC streamer now allows streaming only audio, only video or neither of them, which can be useful in cases where only the exchange of OOB messages is needed. See the JS SDK for details on how to use this feature.
- Anbox now uses
jemallocas memory allocator to improve its overall memory footprint.
- A new OOB version 2 implementation allows bi-directional communication with the Anbox container through the use of data channels. See the documentation for more details. With the introduction of OOB version 2, the former implementation is deprecated and will be removed in a future Anbox Cloud release.
- Added Android security updates for August 2022 (see Android Security Bulletin - August 2022 for more information).
- Updated the Android WebView to 103.0.5060.129.
- Updated the Mesa graphics driver stack to 22.0.5.
ashmemkernel module is now optional for all supported Android versions. Anbox Cloud will drop support for
ashmemwith the 1.18 release.
Anbox Stream Gateway / Agent
- Updated Dqlite to its latest 1.11.1 release.
- The appliance now supports deployment on Ubuntu 22.04.
- The minimum required storage size is now 20 GB.
- On Ubuntu 22.04, the NVIDIA driver is now installed from the Ubuntu archive on arm64 systems instead of from the NVIDIA CUDA archive.
Anbox Cloud tests
- The WebRTC benchmark tool (
anbox-cloud-tests.benchmark) can now:
- Attach to existing sessions (
- Mark sessions to be kept alive after the benchmark is done (
- Set the WebRTC log level to gain low-level insight (
- Attach to existing sessions (
- AC-1036 A native crash happens when streaming from the camera on Safari (iOS device)
- AC-1034 Fix race condition between
init.ranchu.rcand SurfaceFlinger causing a crash
- AC-1028 User-defined resources are overridden when both
resourcesspecs are specified in
- AC-1015 Can’t access the service that is exposed internally over IP forward
- AC-1003 The network endpoint and port persist in the database even after the container is deleted from AMS
- AC-966 Anbox tries to initialise the video decoder when a stream is being established