How to use adb (Android debugging bridge) on Silverblue?

I’ve tried to use adb in a toolbox container (just install it via dnf install android-tools etc. inside of the container), but it seems it is too isolated from the host, because while it can detect a device, it cannot get a permission. Even in Android’s recovery and with sudo in the container it only shows this:

$ sudo adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
4e1d2a26	no permissions; see [http://developer.android.com/tools/device.html]

So should I just give up and layer it on the host instead, or (how) can I make it work inside of the container?

You don’t even need to layer them, as long as you’re okay updating them manually when you need too.

wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip platform-tools-latest-linux.zip
sudo cp -v platform-tools/adb platform-tools/fastboot platform-tools/mke2fs* platform-tools/e2fsdroid /usr/local/bin

To fix perms

git clone https://github.com/M0Rf30/android-udev-rules.git
cd android-udev-rules
sudo cp -v 51-android.rules /etc/udev/rules.d/51-android.rules
sudo chmod a+r /etc/udev/rules.d/51-android.rules
sudo groupadd adbusers
sudo usermod -a -G adbusers $(whoami)
sudo systemctl restart systemd-udevd.service
adb kill-server
adb devices

The udev rules might actually fix them in toolbox.