Error on Ubuntu-24.04

[ViliusSutkus89]

Hello,

First of all, emulators on Linux images are pretty cool. Having said that, I've noticed an issue - it doesn't work on Ubuntu-24.04 (beta). We need to use Ubuntu-22.04 (latest).

Just wanted to file this as an issue, because it took me some time to figure out why my CI is red.

Here's a sample run with Ubuntu-22.04 and Ubuntu-24.04 - https://github.com/ViliusSutkus89/android-emulator-runner-ubuntu-24.04/actions/runs/9594927854

Ubuntu-24.04 errors out:

2024-06-20T09:23:17.9214746Z [command]/usr/bin/sh -c \echo no | avdmanager create avd --force -n test --abi 'default/x86' --package 'system-images;android-29;default;x86'
2024-06-20T09:23:18.6029378Z Loading local repository...                                                     
2024-06-20T09:23:18.6035642Z [=========                              ] 25% Loading local repository...       
2024-06-20T09:23:18.6036583Z [=========                              ] 25% Fetch remote repository...        
2024-06-20T09:23:18.6045879Z [=======================================] 100% Fetch remote repository...       
2024-06-20T09:23:18.7430306Z Do you wish to create a custom hardware profile? [no] [command]/usr/bin/sh -c \printf 'hw.cpu.ncore=2
2024-06-20T09:23:18.7431804Z ' >> /home/runner/.android/avd/test.avd/config.ini
2024-06-20T09:23:18.7449816Z /usr/bin/sh: 1: cannot create /home/runner/.android/avd/test.avd/config.ini: Directory nonexistent
2024-06-20T09:23:18.7456105Z ##[endgroup]
2024-06-20T09:23:18.7457248Z ##[group]Terminate Emulator

Workflow file:

name: CI
on: push
jobs:
  build:
    runs-on: ${{ matrix.os }}
    strategy:
      fail-fast: false
      matrix:
        os:
          - ubuntu-22.04
          - ubuntu-24.04
    steps:
      - name: Enable KVM group perms
        run: |
          echo 'KERNEL=="kvm", GROUP="kvm", MODE="0666", OPTIONS+="static_node=kvm"' | sudo tee /etc/udev/rules.d/99-kvm4all.rules
          sudo udevadm control --reload-rules
          sudo udevadm trigger --name-match=kvm

      - uses: reactivecircus/android-emulator-runner@v2
        with:
          api-level: 29
          script: /bin/true

[hfhbd]

Is there any workaround?

[torokati44]

I also ran into this.
Seems like #327 could fix this...?

[mikehardy]

At its heart it is an environment variable problem. With some console.logs from a forked version of this repo you can see that the AVD-related pathing is messed up for some reason:

https://github.com/ankidroid/Anki-Android-Backend/actions/runs/11281139144/job/31383662978#step:4:90

  /usr/bin/sh -c \echo no | avdmanager create avd --force -n test --abi 'default/x86_64' --package 'system-images;android-23;default;x86_64' --device 'Nexus 6'
  Loading local repository...                                                     
  [=========                              ] 25% Loading local repository...       
  [=========                              ] 25% Fetch remote repository...        
  [=======================================] 100% Fetch remote repository...       
  /usr/bin/sh -c avdmanager list avd
  Available Android Virtual Devices:
      Name: test
    Device: Nexus 6 (Google)
      Path: /home/runner/.config/.android/avd/test.avd

What is that ??

  Path: /home/runner/.config/.android/avd/test.avd

...there is an extra .config path segment in there that shouldn't be.

I'll post a PR that patches it up here but I think you could add this to an env block in your workflow and it might fix things:

ANDROID_USER_HOME: /home/runner/.android
ANDROID_EMULATOR_HOME: /home/runner/.android
ANDROID_AVD_HOME: /home/runner/.android/avd

(from here https://developer.android.com/tools/variables#envar)

When I set those in my forked + fixed version of the action things started working https://github.com/ankidroid/Anki-Android-Backend/actions/runs/11281139144/job/31384483722

[ychescale9]

@mikehardy thanks for the investigation. From my testing it seems like it's due to the following directory no longer ${process.env.HOME}/.android/avd being available with the new 24.04 image.

After creating the directory the tests started working: https://github.com/ReactiveCircus/android-emulator-runner/actions/runs/11284138596/job/31384839511

[mikehardy]

that's strange @ychescale9 because I didn't have to create the directory to get it working, I just had to define the env vars 😆 - I just about have the commits lined up and a PR for it - obviously if you've got it fixed then that's fine to close, but a published vs of the fork with just env vars defined did work.