[GH-ISSUE #101] Unable to run latest image (3 ways) #83

New issue

Closed

opened 2026-02-27 22:07:50 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 22:07:50 +03:00

Owner

Originally created by @MdeLv on GitHub (Nov 2, 2020).
Original GitHub issue: https://github.com/sickcodes/Docker-OSX/issues/101

I was unable to get started with the latest image:

from a DSM synology which has docker integrated (the container stopped in an unexpected way ; no more details)
from a debian10 VM / docker hosted on the DSM
from a debian 10 /docker on a physical motherboard (on going test ; not enough space in var/ ...)

From the VM debian10, here are the 2 trials (I'm not fully aware if the commands are correct)
Can you give some hints to get this image up&running?
Thanks.

$ sudo docker run --device /dev/kvm --device /dev/snd -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}"     sickcodes/docker-osx:latest
docker: Error response from daemon: error gathering device information while adding custom device "/dev/kvm": no such file or directory.
ERRO[0003] error waiting for container: context canceled 

$ sudo docker run --privileged -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix sickcodes/docker-osx
ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519 
No protocol specified
Unable to init server: Could not connect: Connection refused
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
QEMU 5.1.0 monitor - type 'help' for more information
(qemu) qemu-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory

Originally created by @MdeLv on GitHub (Nov 2, 2020). Original GitHub issue: https://github.com/sickcodes/Docker-OSX/issues/101 I was unable to get started with the latest image: - from a DSM synology which has docker integrated (the container stopped in an unexpected way ; no more details) - from a debian10 VM / docker hosted on the DSM - from a debian 10 /docker on a physical motherboard (on going test ; not enough space in var/ ...) From the VM debian10, here are the 2 trials (I'm not fully aware if the commands are correct) Can you give some hints to get this image up&running? Thanks. ``` $ sudo docker run --device /dev/kvm --device /dev/snd -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" sickcodes/docker-osx:latest docker: Error response from daemon: error gathering device information while adding custom device "/dev/kvm": no such file or directory. ERRO[0003] error waiting for container: context canceled $ sudo docker run --privileged -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix sickcodes/docker-osx ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519 No protocol specified Unable to init server: Could not connect: Connection refused Could not access KVM kernel module: No such file or directory qemu-system-x86_64: failed to initialize kvm: No such file or directory qemu-system-x86_64: falling back to tcg QEMU 5.1.0 monitor - type 'help' for more information (qemu) qemu-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory ```