You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're working on signalapp/ringrtc#61 to build Signal's RingRTC on native Linux arm64 runners.
However, we're observing a weird difference between the new ubuntu-22.04-arm runner that's now in Public Preview and larger (org-level) Ubuntu 22.04 runners. According to the GitHub documentation, they should be using the exact same Ubuntu 22.04 Partner Images and therefore should behave consistently. That doesn't seem to be the case.
Confirming that my org-level ubuntu-22.04-arm-dennis is using the Ubuntu 22.04 by Arm Limited image and not a custom one:
Here you can see the difference for the exact same pipeline:
Using the ubuntu-22.04-arm Public Preview runner, the "Install dependencies" step works without problems.
Using the ubuntu-22.04-arm-dennis (org-level) runner, the "Install dependencies" fails with:
Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user)
Error: Process completed with exit code 1.
Could it be that there's a difference between the machines or images that run on the new Public Preview runners vs. the larger org-level ones? Thanks!
dennisameling
changed the title
DBUS_SESSION_BUS_ADDRESS error on Linux arm64 22.04 larger runnerDBUS_SESSION_BUS_ADDRESS / XDG_RUNTIME_DIR error on Linux arm64 22.04 larger runner
Feb 23, 2025
Was just comparing the output of env on the ubuntu-22.04-arm vs. the ubuntu-22.04-arm-dennis runner and noticed that XDG_RUNTIME_DIR is indeed missing on the larger runner:
There seems to be a slight config change on the ubuntu-22.04-arm runner vs the larger runners.
steps:
# https://github.com/actions/partner-runner-images/issues/53
- name: Work around XDG_RUNTIME_DIR error on Linux arm64if: startsWith(matrix.os, 'ubuntu-22.04-arm')run: | echo "UID is $UID. Setting XDG_RUNTIME_DIR to /run/user/$UID" sudo systemctl start user@$UID.service echo "XDG_RUNTIME_DIR=/run/user/$UID" >> $GITHUB_ENV
@maxim-lobanov given that you or your team fixed the issue with XDG_CONFIG_HOME in a probably slightly related issue, I'm tagging you here if that's OK. Do you have any thoughts on this?
We're working on signalapp/ringrtc#61 to build Signal's RingRTC on native Linux arm64 runners.
However, we're observing a weird difference between the new
ubuntu-22.04-arm
runner that's now in Public Preview and larger (org-level) Ubuntu 22.04 runners. According to the GitHub documentation, they should be using the exact same Ubuntu 22.04 Partner Images and therefore should behave consistently. That doesn't seem to be the case.Confirming that my org-level
ubuntu-22.04-arm-dennis
is using theUbuntu 22.04 by Arm Limited image
and not a custom one:Here you can see the difference for the exact same pipeline:
ubuntu-22.04-arm
Public Preview runner, the "Install dependencies" step works without problems.ubuntu-22.04-arm-dennis
(org-level) runner, the "Install dependencies" fails with:Could it be that there's a difference between the machines or images that run on the new Public Preview runners vs. the larger org-level ones? Thanks!
Reproduction steps
Pipeline using the public ubuntu-22.04-arm runner: https://github.com/dennisameling/ringrtc/blob/refs/heads/arm64-native-tmp/.github/workflows/ringrtc.yml#L113
Pipeline using org-level larger ubuntu-22.04-arm-dennis runner: https://github.com/dennisameling-org/ringrtc/blob/arm64-native-tmp/.github/workflows/ringrtc.yml#L114
The text was updated successfully, but these errors were encountered: