Error response from daemon: error gathering device information while adding custom device "/dev/kvm": no such file or directory. #470

New Issue

adam · 2025-12-29T06:20:19+01:00

adam commented

2025-12-29 06:20:19 +01:00

Originally created by @AzeemQidwai on GitHub (Feb 5, 2023).

I am getting the error while trying to run Ventura image. Details of my OS is as follows.

NAME="Ubuntu"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdb1        94G   57G   33G  64% /
QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.6)
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
libvirtd (libvirt) 8.0.0
               total        used        free      shared  buff/cache   available
Mem:           7.6Gi       2.2Gi       247Mi       3.9Gi       5.2Gi       1.2Gi
Swap:           19Gi       1.0Gi        18Gi
4
8
crw-rw----+ 1 root kvm 10, 232 Feb  5 23:56 /dev/kvm
total 16K
drwxrwxrwt  2 root  root  4.0K Feb  5 23:53 .
drwxrwxrwt 28 root  root   12K Feb  6 00:51 ..
srwxrwxrwx  1 azeem azeem    0 Feb  5 23:53 X0
srwxrwxr-x  1 gdm   gdm      0 Feb  5 23:53 X1024
srwxrwxr-x  1 gdm   gdm      0 Feb  5 23:53 X1025
root        1455  0.0  0.2 1392636 18652 ?       Ssl  Feb05   0:01 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
azeem      11728  0.0  0.0   9560  2224 pts/0    S+   00:54   0:00 grep --color=auto dockerd

Originally created by @AzeemQidwai on GitHub (Feb 5, 2023). I am getting the error while trying to run Ventura image. Details of my OS is as follows. ```PRETTY_NAME="Ubuntu 22.04.1 LTS" NAME="Ubuntu" VERSION_CODENAME=jammy UBUNTU_CODENAME=jammy Filesystem Size Used Avail Use% Mounted on /dev/sdb1 94G 57G 33G 64% / QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.6) Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers libvirtd (libvirt) 8.0.0 total used free shared buff/cache available Mem: 7.6Gi 2.2Gi 247Mi 3.9Gi 5.2Gi 1.2Gi Swap: 19Gi 1.0Gi 18Gi 4 8 crw-rw----+ 1 root kvm 10, 232 Feb 5 23:56 /dev/kvm total 16K drwxrwxrwt 2 root root 4.0K Feb 5 23:53 . drwxrwxrwt 28 root root 12K Feb 6 00:51 .. srwxrwxrwx 1 azeem azeem 0 Feb 5 23:53 X0 srwxrwxr-x 1 gdm gdm 0 Feb 5 23:53 X1024 srwxrwxr-x 1 gdm gdm 0 Feb 5 23:53 X1025 root 1455 0.0 0.2 1392636 18652 ? Ssl Feb05 0:01 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock azeem 11728 0.0 0.0 9560 2224 pts/0 S+ 00:54 0:00 grep --color=auto dockerd ```

adam commented

2025-12-29 06:20:19 +01:00

@james-tindal commented on GitHub (Feb 6, 2023):

I have the same problem trying to run the Ventura image on Big Sur.

@james-tindal commented on GitHub (Feb 6, 2023): I have the same problem trying to run the Ventura image on Big Sur.

adam commented

2025-12-29 06:20:20 +01:00

@AzeemQidwai commented on GitHub (Feb 7, 2023):

I resolved this issue on Ubuntu. I completely uninstall Docker on Desktop and removed all docker folders and dependencies and reinstall it as per this link. Then try to run Ventura on newly installed docker. It works like a charm.

@AzeemQidwai commented on GitHub (Feb 7, 2023): I resolved this issue on Ubuntu. I completely uninstall Docker on Desktop and removed all docker folders and dependencies and reinstall it as per this [link](https://linuxhandbook.com/install-docker-ubuntu/). Then try to run Ventura on newly installed docker. It works like a charm.

adam referenced this issue

2025-12-29 06:22:49 +01:00

[PR #472] [MERGED] Fixes #470 TEMP-FIX is breaking Dockerfile.nakedvnc build #470 #776

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Docker-OSX-sickcodes#470