starred/Docker-OSX
1
0
Fork 0
mirror of https://github.com/sickcodes/Docker-OSX.git synced 2026-04-28 00:55:49 +03:00
Code Issues 415 Projects Releases Packages Wiki Activity

[GH-ISSUE #650] Docker: Unknown Server OS #490

New issue
Closed
opened 2026-02-27 23:00:47 +03:00 by kerem · 8 comments
kerem commented 2026-02-27 23:00:47 +03:00
Owner
Copy link

Originally created by @vm-hacker on GitHub (Apr 16, 2023).
Original GitHub issue: https://github.com/sickcodes/Docker-OSX/issues/650

I saw this error, when I ran the ventura command given in the README
docker: unknown server OS: .
See 'docker run --help'.

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 build -t docker-osx --build-arg SHORTNAME=ventura .

This is occuring across all linux distros I tried

Originally created by @vm-hacker on GitHub (Apr 16, 2023). Original GitHub issue: https://github.com/sickcodes/Docker-OSX/issues/650 I saw this error, when I ran the ventura command given in the README docker: unknown server OS: . See 'docker run --help'. 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 build -t docker-osx --build-arg SHORTNAME=ventura . This is occuring across all linux distros I tried
kerem closed this issue 2026-02-27 23:00:47 +03:00
kerem commented 2026-02-27 23:00:47 +03:00
Author
Owner
Copy link

@h113331pp commented on GitHub (Apr 17, 2023):

This is probably your docker daemon is not running.
For fast check, open another terminal and run dockerd then try again.

Edit:
before do above, just use ps command to see if your docker daemon is running or not:
ps aux | grep dockerd

<!-- gh-comment-id:1510607218 --> @h113331pp commented on GitHub (Apr 17, 2023): This is probably your docker daemon is not running. For fast check, open another terminal and run **dockerd** then try again. Edit: before do above, just use ps command to see if your docker daemon is running or not: `ps aux | grep dockerd`
kerem commented 2026-02-27 23:00:47 +03:00
Author
Owner
Copy link

@vm-hacker commented on GitHub (Apr 17, 2023):

root 1155 0.0 0.2 1742976 64796 ? Ssl 06:55 0:01 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
brain 12665 0.0 0.0 11740 2704 pts/2 S+ 10:21 0:00 grep --color=auto dockerd

<!-- gh-comment-id:1510694030 --> @vm-hacker commented on GitHub (Apr 17, 2023): root 1155 0.0 0.2 1742976 64796 ? Ssl 06:55 0:01 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock brain 12665 0.0 0.0 11740 2704 pts/2 S+ 10:21 0:00 grep --color=auto dockerd
kerem commented 2026-02-27 23:00:47 +03:00
Author
Owner
Copy link

@vm-hacker commented on GitHub (Apr 17, 2023):

systemctl status docker returns

● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2023-04-17 06:55:29 +0530; 3h 26min ago
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Main PID: 1155 (dockerd)
Tasks: 14
Memory: 103.7M
CPU: 1.412s
CGroup: /system.slice/docker.service
└─1155 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

<!-- gh-comment-id:1510694302 --> @vm-hacker commented on GitHub (Apr 17, 2023): systemctl status docker returns ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2023-04-17 06:55:29 +0530; 3h 26min ago TriggeredBy: ● docker.socket Docs: https://docs.docker.com Main PID: 1155 (dockerd) Tasks: 14 Memory: 103.7M CPU: 1.412s CGroup: /system.slice/docker.service └─1155 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
kerem commented 2026-02-27 23:00:47 +03:00
Author
Owner
Copy link

@h113331pp commented on GitHub (Apr 17, 2023):

OK, It seems the docker daemon is running well.
Did you also setup your user account is in the group docker?
https://docs.docker.com/engine/install/linux-postinstall/

Or you just use "sudo" everytime when call "docker run -it ..."?

<!-- gh-comment-id:1511354726 --> @h113331pp commented on GitHub (Apr 17, 2023): OK, It seems the docker daemon is running well. Did you also setup your user account is in the group docker? https://docs.docker.com/engine/install/linux-postinstall/ Or you just use "sudo" everytime when call "docker run -it ..."?
kerem commented 2026-02-27 23:00:47 +03:00
Author
Owner
Copy link

@sonicdevo commented on GitHub (Apr 24, 2023):

I, too and running into the same error with the same troubleshooting results.

EDIT: Solved. Looks like I neglected to finish the post-install instructions. More clearly outlined here: https://stackoverflow.com/questions/48957195/how-to-fix-docker-got-permission-denied-issue

<!-- gh-comment-id:1520580830 --> @sonicdevo commented on GitHub (Apr 24, 2023): I, too and running into the same error with the same troubleshooting results. EDIT: Solved. Looks like I neglected to finish the post-install instructions. More clearly outlined here: https://stackoverflow.com/questions/48957195/how-to-fix-docker-got-permission-denied-issue
kerem commented 2026-02-27 23:00:47 +03:00
Author
Owner
Copy link

@sickcodes commented on GitHub (May 7, 2023):

Is this snap docker on Ubuntu? If so, kill it, and install the real one.

<!-- gh-comment-id:1537430406 --> @sickcodes commented on GitHub (May 7, 2023): Is this snap docker on Ubuntu? If so, kill it, and install the real one.
kerem commented 2026-02-27 23:00:48 +03:00
Author
Owner
Copy link

@vm-hacker commented on GitHub (Jun 20, 2023):

It's not the snap, it's the docker.io package

<!-- gh-comment-id:1598139963 --> @vm-hacker commented on GitHub (Jun 20, 2023): It's not the snap, it's the docker.io package
kerem commented 2026-02-27 23:00:48 +03:00
Author
Owner
Copy link

@vm-hacker commented on GitHub (Jun 20, 2023):

I found a solution, sorry I just ignored the step of creating a docker user group and then logging out
https://docs.docker.com/engine/install/linux-postinstall/

<!-- gh-comment-id:1598144070 --> @vm-hacker commented on GitHub (Jun 20, 2023): I found a solution, sorry I just ignored the step of creating a docker user group and then logging out https://docs.docker.com/engine/install/linux-postinstall/
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
tahoe
sequoia
runtime-download
mouse-fix
sonoma
ventura
naked-vnc-legacy-patch
persistent
rollback-naked
shrink-naked
mojave-high-sierra
libguestfs-linux-hold
netdev
stock-images-in-dockerfile
monterey
naked-auto
cpu-max-features
glibc-revert-wip
file-downgrade-all-images
osx-serial-update
custom-plist-always
custom-identity
No results found.
Labels
Clear labels   
bug

   
documentation

   
enhancement

   
following upstream developments

   
good first issue

   
help wanted

   
invalid

   
pull-request

Mirrored from GitHub Pull Request

  
question
No labels
bug
documentation
enhancement
following upstream developments
good first issue
help wanted
invalid
pull-request
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Docker-OSX#490
No description provided.