Launch errors

[brauliobo]

Using acceleration command example:

docker run -it \
    --privileged \
    --device /dev/kvm \
    -v /tmp/.X11-unix:/tmp/.X11-unix \
    -e "DISPLAY=${DISPLAY:-:0.0}" \
    -p 5555:5555 \
    -p 50922:10022 \
    --device=/dev/dri \
    --group-add video \
    -e EXTRA='-display sdl,gl=on' \
    sickcodes/dock-droid:latest &> /tmp/accel-log.txt

Last lines of log:

alsa: Could not initialize ADC
alsa: Failed to open `default':
alsa: Reason: No such file or directory
audio: Failed to create voice `adc'
Authorization required, but no authorization protocol specified
Could not initialize SDL(x11 not available) - exiting

Full log: accel-log.txt

Below is the execution of the basic example command:

docker run -it \
    --device /dev/kvm \
    -v /tmp/.X11-unix:/tmp/.X11-unix \
    -e "DISPLAY=${DISPLAY:-:0.0}" \
    -p 5555:5555 \
    sickcodes/dock-droid:latest &> /tmp/log.txt

Last lines of the log:

alsa: Could not initialize ADC
alsa: Failed to open `default':
alsa: Reason: No such file or directory
audio: Failed to create voice `adc'
gtk initialization failed

Full log: log.txt

[tech128]

well i was tryin to get this to work yesterday and had the same problem using kali linux. it seems the issue is your distro does not use alsa but probably uses pipewire or pulseaudio instead. what i did since i'm just trying to get this to work, is i added -e AUDIO_DRIVER='none' into the docker command and it loaded without audio. if you knew the right syntax, you could probably get it to properly use pulseaudio or pipewire, but you'd need to find out what your distro uses first.

[AndroidMaster24]

Still can't launch for me even with no audio flag. I'm using Linux mint 21.1 with X11 display

dell@dell-OptiPlex-7010:~$ docker run -it     --device /dev/kvm     -v /tmp/.X11-unix:/tmp/.X11-unix     -e "DISPLAY=${DISPLAY:-:0}"     -p 5555:5555   -e AUDIO_DRIVER='none'     sickcodes/dock-droid:latest

ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519 
nohup: appending output to 'nohup.out'
+ source /etc/profile.d/android-sdk-platform-tools.sh
++ export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/android-sdk/platform-tools:/opt/android-sdk/platform-tools
++ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/android-sdk/platform-tools:/opt/android-sdk/platform-tools
++ id -u
++ id -g
+ sudo chown 1000:1000 /dev/kvm
++ id -u
++ id -g
+ sudo chown -R 1000:1000 /dev/snd
+ true
++ id -u
++ id -g
+ sudo chown -R 1000:1000 /dev/video0 /dev/video1 /dev/video2 /dev/video3 /dev/video4 /dev/video5 /dev/video6 /dev/video7 /dev/video8 /dev/video9 /dev/video10
+ true
++ nproc
+ sudo qemu-system-x86_64 -m 4000 -enable-kvm -cpu host,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check, -smp 4 -machine q35,accel=kvm:tcg -smp 4,cores=4 -hda /home/arch/dock-droid/android.qcow2 -usb -device usb-kbd -device usb-tablet -smbios type=2 -audiodev none,id=hda -device ich9-intel-hda -device hda-duplex,audiodev=hda -device usb-ehci,id=ehci -netdev user,id=net0,hostfwd=tcp::10022-:22,hostfwd=tcp::5900-:5900,hostfwd=tcp::5555-:5555, -device vmxnet3,netdev=net0,id=net0,mac=00:11:22:33:44:55 -monitor stdio -boot menu=on -cdrom Bliss-v11.13--OFFICIAL-20201113-1525_x86_64_k-k4.19.122-ax86-ga-rmi_m-20.1.0-llvm90_dgc-t3_gms_intelhd.iso -vga vmware
Authorization required, but no authorization protocol specified
QEMU 6.2.0 monitor - type 'help' for more information
(qemu) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.aes [bit 25]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.aes [bit 25]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.aes [bit 25]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.aes [bit 25]
gtk initialization failed

[1RandomDev]

Still can't launch for me even with no audio flag. I'm using Linux mint 21.1 with X11 display

Same on Fedora 39. Running xhost + before starting the container seems to work, but doesn't fix the sound error.