Open tokenwizard opened 3 months ago
I tried updating my run command to use PulseAudio by adding these lines:
-e AUDIO_DRIVER=pa,server=unix:/tmp/pulseaudio.socket \
-v "/run/user/$(id -u)/pulse/native:/tmp/pulseaudio.socket" \
-e PULSE_SERVER=unix:/tmp/pulseaudio.socket \
and now it no longer shows the ALSA-related errors, but still exits, whether run with sudo or not.
docker-osx-1 | + exec qemu-system-x86_64 -m 4000 -cpu Haswell-noTSX,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on -machine q35,accel=kvm:tcg -smp 4,cores=4 -device qemu-xhci,id=xhci -device usb-kbd,bus=xhci.0 -device usb-tablet,bus=xhci.0 -device 'isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc' -drive if=pflash,format=raw,readonly=on,file=/home/arch/OSX-KVM/OVMF_CODE.fd -drive if=pflash,format=raw,file=/home/arch/OSX-KVM/OVMF_VARS-1024x768.fd -smbios type=2 -audiodev pa,server=unix:/tmp/pulseaudio.socket,id=hda -device ich9-intel-hda -device hda-duplex,audiodev=hda -device ich9-ahci,id=sata -drive id=OpenCoreBoot,if=none,snapshot=on,format=qcow2,file=/home/arch/OSX-KVM/OpenCore/OpenCore.qcow2 -device ide-hd,bus=sata.2,drive=OpenCoreBoot -device ide-hd,bus=sata.3,drive=InstallMedia -drive id=InstallMedia,if=none,file=/home/arch/OSX-KVM/BaseSystem.img,format=qcow2 -drive id=MacHDD,if=none,file=/home/arch/OSX-KVM/mac_hdd_ng.img,format=qcow2 -device ide-hd,bus=sata.4,drive=MacHDD -netdev user,id=net0,hostfwd=tcp::10022-:22,hostfwd=tcp::5900-:5900, -device vmxnet3,netdev=net0,id=net0,mac=52:54:00:09:49:17 -monitor stdio -boot menu=on -vga vmware
docker-osx-1 | Authorization required, but no authorization protocol specified
docker-osx-1 |
docker-osx-1 | pulseaudio: pa_context_connect() failed
docker-osx-1 | pulseaudio: Reason: Connection refused
docker-osx-1 | pulseaudio: Failed to initialize PA contextqemu-system-x86_64: could not connect to PulseAudio server
docker-osx-1 exited with code 1
I was able to get around this by following the steps in https://github.com/sickcodes/Docker-OSX/issues/7#issuecomment-639356240 on my host.
ALSA is not related and happens to everyone, according to README. The real error is the last line, "gtk initialization failed," which is most likely about how you set up your display. Please provide your docker command for further troubleshoot. you should also check if you're using wayland or X. There're many issues about X already. i'm using Wayland, and one important thing is /run/user/{UID} has been given enough permission.
Requested info is logged below. Also, I put the console output that seemed relevant (ALSA errors just before the system exists with the gtk initialization error).
Is ALSA a prerequisite for this to work? Is there something else I'm missing?
I regularly run other docker containers on this system.
OS related issued, please help us identify the issue by posting the output of this
uname -a \
Linux OfficePC 6.9.9-1-MANJARO #1 SMP PREEMPT_DYNAMIC Fri Jul 12 10:32:52 UTC 2024 x86_64 GNU/Linux
; echo "${DISPLAY}" \
:0.0
; echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs \
1
; grep NAME /etc/os-release \
; df -h . \
; qemu-system-x86_64 --version \
; libvirtd --version \
libvirtd (libvirt) 10.5.0
; free -mh \
; nproc \
16
; egrep -c '(svm|vmx)' /proc/cpuinfo \
; ls -lha /dev/kvm \
crw-rw-rw- 1 root kvm 10, 232 Jul 31 11:15 /dev/kvm
; ls -lha /tmp/.X11-unix/ \
; ps aux | grep dockerd \
; docker ps | grep osx \ (NULL)
; grep "docker|kvm|virt" /etc/group
Seemingly-relevant log output: