Originally created by @superbonaci on GitHub (Dec 7, 2022).
On Arch:
$ sudo pacman -Suy docker
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (3) containerd-1.6.10-1 runc-1.1.4-1 docker-1:20.10.21-1
Total Download Size: 54.43 MiB
Total Installed Size: 237.83 MiB
:: Proceed with installation? [Y/n] y
Then try to run it:
$ docker run -it \
--device /dev/kvm \
-p 50922:10022 \
-v /tmp/.X11-unix:/tmp/.X11-unix \
-e "DISPLAY=${DISPLAY:-:0.0}" \
-e GENERATE_UNIQUE=true \
-e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \
sickcodes/docker-osx:ventura
docker: unknown server OS: .
See 'docker run --help'.
Originally created by @superbonaci on GitHub (Dec 7, 2022).
On Arch:
```
$ sudo pacman -Suy docker
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (3) containerd-1.6.10-1 runc-1.1.4-1 docker-1:20.10.21-1
Total Download Size: 54.43 MiB
Total Installed Size: 237.83 MiB
:: Proceed with installation? [Y/n] y
```
Then try to run it:
```
$ docker run -it \
--device /dev/kvm \
-p 50922:10022 \
-v /tmp/.X11-unix:/tmp/.X11-unix \
-e "DISPLAY=${DISPLAY:-:0.0}" \
-e GENERATE_UNIQUE=true \
-e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \
sickcodes/docker-osx:ventura
docker: unknown server OS: .
See 'docker run --help'.
```
For me it was a permission issue with /var/run/docerk.sock. If you run docker ps, you will see this error, but docker run somehow suppresses the real error behind the failure.
Solved by
sudo usermod -aG docker $USER
newgrp docker
@tautomer commented on GitHub (Sep 24, 2025):
For me it was a permission issue with `/var/run/docerk.sock`. If you run `docker ps`, you will see this error, but `docker run` somehow suppresses the real error behind the failure.
Solved by
```shell
sudo usermod -aG docker $USER
newgrp docker
```
$ docker run --rm hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
17eec7bbc9d7: Pull complete
Digest: sha256:54e66cc1dd1fcb1c3c58bd8017914dbed8701e2d8c74d9262e26bd9cc1642d31
Status: Downloaded newer image for hello-world:latest
Hello from Docker!
This message shows that your installation appears to be working correctly.
To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
(amd64)
3. The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
4. The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.
To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash
Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/
For more examples and ideas, visit:
https://docs.docker.com/get-started/
/dev/kvm must exist:
$ ls -l /dev/kvm
crw-rw-rw- 1 root kvm 10, 232 Jan 24 10:53 /dev/kvm
ventura does not work this way:
$ docker run -it \
--device /dev/kvm \
-p 50922:10022 \
-v /tmp/.X11-unix:/tmp/.X11-unix \
-e "DISPLAY=${DISPLAY:-:0.0}" \
-e GENERATE_UNIQUE=true \
-e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \
sickcodes/docker-osx:ventura
Unable to find image 'sickcodes/docker-osx:ventura' locally
docker: Error response from daemon: manifest for sickcodes/docker-osx:ventura not found: manifest unknown: manifest unknown
Run 'docker run --help' for more information
I'm going to close this issue since works for me. Please comment to reopen if anyone else still has issues.
@superbonaci commented on GitHub (Sep 24, 2025):
I'm going to close this issue since works for me. Please comment to reopen if anyone else still has issues.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @superbonaci on GitHub (Dec 7, 2022).
On Arch:
Then try to run it:
@dkornahrens commented on GitHub (Dec 8, 2022):
Same mileage.
Edit: I didn't read. https://github.com/sickcodes/Docker-OSX#initial-setup
@superbonaci commented on GitHub (Dec 8, 2022):
@dkornahrens does work with you after initial setup or still same issue?
@Badirkhanov commented on GitHub (Jan 13, 2023):
This helped me: https://github.com/sickcodes/Docker-OSX#docker-unknown-server-os-error
@tautomer commented on GitHub (Sep 24, 2025):
For me it was a permission issue with
/var/run/docerk.sock. If you rundocker ps, you will see this error, butdocker runsomehow suppresses the real error behind the failure.Solved by
@superbonaci commented on GitHub (Sep 24, 2025):
Updated to
docker-1:28.4.0-1.Fixed running this:
Now the info should be available:
Hello world should work:
/dev/kvm must exist:
ventura does not work this way:
Has to be called this way:
@superbonaci commented on GitHub (Sep 24, 2025):
I'm going to close this issue since works for me. Please comment to reopen if anyone else still has issues.