Can't run OS X inside of OS X #4

New Issue

2025-12-29T05:19:17+01:00

adam commented

2025-12-29 05:19:17 +01:00

Originally created by @tibbon on GitHub (Jun 5, 2020).

No host support it seems

docker run --privileged -v /tmp/.X11-unix:/tmp/.X11-unix sickcodes/docker-osx
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

Originally created by @tibbon on GitHub (Jun 5, 2020). No host support it seems ``` docker run --privileged -v /tmp/.X11-unix:/tmp/.X11-unix sickcodes/docker-osx 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 ```

adam commented

2025-12-29 05:19:19 +01:00

@kongminhao commented on GitHub (Jun 5, 2020):

matryoshka forbidden.

@kongminhao commented on GitHub (Jun 5, 2020): matryoshka forbidden.

adam commented

2025-12-29 05:19:19 +01:00

@suda commented on GitHub (Jun 5, 2020):

It probably won't be possible to run it on macOS as Docker for Mac is actually running a tiny Linux VM with Docker inside, so the "matryoshka" would even be deeper.

@suda commented on GitHub (Jun 5, 2020): It probably won't be possible to run it on macOS as Docker for Mac is actually running a tiny Linux VM with Docker inside, so the "matryoshka" would even be deeper.

adam commented

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

@sickcodes commented on GitHub (Jun 5, 2020):

No host support it seems

docker run --privileged -v /tmp/.X11-unix:/tmp/.X11-unix sickcodes/docker-osx
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

Try this:

echo $DISPLAY

# ARCH
sudo pacman -S xorg-xhost

# UBUNTU DEBIAN
sudo apt install x11-xserver-utils

# CENTOS RHEL FEDORA
sudo yum install xorg-x11-server-utils

# then run
xhost +

docker run --privileged -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix sickcodes/docker-osx ./OpenCore-Boot.sh

@sickcodes commented on GitHub (Jun 5, 2020): > No host support it seems > > ``` > docker run --privileged -v /tmp/.X11-unix:/tmp/.X11-unix sickcodes/docker-osx > 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 > ``` Try this: ``` echo $DISPLAY # ARCH sudo pacman -S xorg-xhost # UBUNTU DEBIAN sudo apt install x11-xserver-utils # CENTOS RHEL FEDORA sudo yum install xorg-x11-server-utils # then run xhost + docker run --privileged -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix sickcodes/docker-osx ./OpenCore-Boot.sh ```

adam commented

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

@sickcodes commented on GitHub (Jun 5, 2020):

I can put up VNC version if you want, the original I had was VNC before I saw how someone else did the x11 fowarding

@sickcodes commented on GitHub (Jun 5, 2020): I can put up VNC version if you want, the original I had was VNC before I saw how someone else did the x11 fowarding

adam commented

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

@romancin commented on GitHub (Jun 5, 2020):

I can put up VNC version if you want, the original I had was VNC before I saw how someone else did the x11 fowarding

It would be awesome for running macOS Server on a headless server.

@romancin commented on GitHub (Jun 5, 2020): > I can put up VNC version if you want, the original I had was VNC before I saw how someone else did the x11 fowarding It would be awesome for running macOS Server on a headless server.

adam commented

2025-12-29 05:19:21 +01:00

@sickcodes commented on GitHub (Jun 6, 2020):

Got it ready, will post in about three hours 😎

@sickcodes commented on GitHub (Jun 6, 2020): Got it ready, will post in about three hours 😎

adam commented

2025-12-29 05:19:22 +01:00

@sickcodes commented on GitHub (Jun 7, 2020):

https://github.com/sickcodes/Docker-OSX/tree/master/vnc-version

@sickcodes commented on GitHub (Jun 7, 2020): https://github.com/sickcodes/Docker-OSX/tree/master/vnc-version

adam commented

2025-12-29 05:19:22 +01:00

@tibbon commented on GitHub (Jun 7, 2020):

Awesome, thank you!!!! I was almost just asking for a joke, but it does seem useful now that I think of it!

@tibbon commented on GitHub (Jun 7, 2020): Awesome, thank you!!!! I was almost just asking for a joke, but it does seem useful now that I think of it!

adam commented

2025-12-29 05:19:22 +01:00

@sickcodes commented on GitHub (Jun 7, 2020):

You’re welcome, just promise to show us a screenshot once you get it running :)!

@sickcodes commented on GitHub (Jun 7, 2020): You’re welcome, just promise to show us a screenshot once you get it running :)!

adam commented

2025-12-29 05:19:23 +01:00

@sickcodes commented on GitHub (Jun 8, 2020):

Let us know if it worked guys :)

@sickcodes commented on GitHub (Jun 8, 2020): Let us know if it worked guys :)

adam commented

2025-12-29 05:19:23 +01:00

@sickcodes commented on GitHub (Jun 10, 2020):

Leaving this open until someone confirms

matryoshka

@sickcodes commented on GitHub (Jun 10, 2020): Leaving this open until someone confirms > matryoshka

adam commented

2025-12-29 05:19:23 +01:00

@tibbon commented on GitHub (Jun 10, 2020):

Hmm, I'm getting this error now. Perhaps I'm just doing it wrong?

docker build -t local/docker-osx .
Sending build context to Docker daemon   5.12kB
Step 1/16 : FROM sickcodes/docker-osx:latest
 ---> 330edd24b7ee
Step 2/16 : MAINTAINER 'https://sick.codes' <https://sick.codes>
 ---> Using cache
 ---> 1f9a28c49b1a
Step 3/16 : USER arch
 ---> Using cache
 ---> b3064897f87d
Step 4/16 : RUN sudo pacman -S tigervnc xterm xorg-xhost xdotool ufw --noconfirm
 ---> Using cache
 ---> 3a7f37b66d2d
Step 5/16 : RUN mkdir ${HOME}/.vnc
 ---> Using cache
 ---> c089588609b7
Step 6/16 : RUN printf '%s\n' 'xinit &' 'xterm &' > ~/.vnc/xstartup
 ---> Using cache
 ---> 1b2648e8f176
Step 7/16 : RUN printf '%s\n%s\n%s\n\n' 'export DISPLAY=:99' 'vncserver -kill :99 || true' 'vncserver -geometry 1920x1080 -depth ${DEPTH:=24} -xstartup ~/.vnc/xstartup :99' > vnc.sh
 ---> Using cache
 ---> 89deedc7bcb6
Step 8/16 : RUN cat vnc.sh OpenCore-Boot.sh > OpenCore-Boot_custom.sh
 ---> Using cache
 ---> e21a17a07243
Step 9/16 : RUN chmod +x OpenCore-Boot_custom.sh
 ---> Using cache
 ---> b4f13ef4a4c1
Step 10/16 : RUN tee vncpasswd_file <<< "${VNC_PASSWORD:=$(openssl rand -hex 4)}"
 ---> Using cache
 ---> e7b48d1a15ef
Step 11/16 : RUN vncpasswd -f < vncpasswd_file > ${HOME}/.vnc/passwd
 ---> Using cache
 ---> 266c4cc51c58
Step 12/16 : RUN chmod 600 ~/.vnc/passwd
 ---> Using cache
 ---> af74e65141be
Step 13/16 : RUN printf '\n\n\n\n%s\n%s\n\n\n\n' '===========VNC_PASSWORD========== ' "$(<vncpasswd_file)"
 ---> Using cache
 ---> 93b5440515eb
Step 14/16 : WORKDIR /home/arch/OSX-KVM
 ---> Using cache
 ---> 6aca647168a0
Step 15/16 : USER arch
 ---> Using cache
 ---> 1ab163ce8287
Step 16/16 : CMD ./OpenCore-Boot_custom.sh
 ---> Using cache
 ---> fca260b8ecbf
Successfully built fca260b8ecbf
Successfully tagged local/docker-osx:latest
me@mymac vnc-version % docker run --privileged -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix local/docker-osx ./OpenCore-Boot.sh
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

I did a brew install qemu but I don't think that's my issue?

I also tried:

me@mymac vnc-version % docker run local/docker-osx

Can't find file /home/arch/.vnc/24a99c353255:99.pid
You'll have to kill the Xvnc process manually

xauth:  file /home/arch/.Xauthority does not exist

New '24a99c353255:99 (arch)' desktop is 24a99c353255:99

Creating default config /home/arch/.vnc/config
Starting applications specified in /home/arch/.vnc/xstartup
Log file is /home/arch/.vnc/24a99c353255:99.log

Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: failed to initialize kvm: No such file or directory

@tibbon commented on GitHub (Jun 10, 2020): Hmm, I'm getting this error now. Perhaps I'm just doing it wrong? ``` docker build -t local/docker-osx . Sending build context to Docker daemon 5.12kB Step 1/16 : FROM sickcodes/docker-osx:latest ---> 330edd24b7ee Step 2/16 : MAINTAINER 'https://sick.codes' <https://sick.codes> ---> Using cache ---> 1f9a28c49b1a Step 3/16 : USER arch ---> Using cache ---> b3064897f87d Step 4/16 : RUN sudo pacman -S tigervnc xterm xorg-xhost xdotool ufw --noconfirm ---> Using cache ---> 3a7f37b66d2d Step 5/16 : RUN mkdir ${HOME}/.vnc ---> Using cache ---> c089588609b7 Step 6/16 : RUN printf '%s\n' 'xinit &' 'xterm &' > ~/.vnc/xstartup ---> Using cache ---> 1b2648e8f176 Step 7/16 : RUN printf '%s\n%s\n%s\n\n' 'export DISPLAY=:99' 'vncserver -kill :99 || true' 'vncserver -geometry 1920x1080 -depth ${DEPTH:=24} -xstartup ~/.vnc/xstartup :99' > vnc.sh ---> Using cache ---> 89deedc7bcb6 Step 8/16 : RUN cat vnc.sh OpenCore-Boot.sh > OpenCore-Boot_custom.sh ---> Using cache ---> e21a17a07243 Step 9/16 : RUN chmod +x OpenCore-Boot_custom.sh ---> Using cache ---> b4f13ef4a4c1 Step 10/16 : RUN tee vncpasswd_file <<< "${VNC_PASSWORD:=$(openssl rand -hex 4)}" ---> Using cache ---> e7b48d1a15ef Step 11/16 : RUN vncpasswd -f < vncpasswd_file > ${HOME}/.vnc/passwd ---> Using cache ---> 266c4cc51c58 Step 12/16 : RUN chmod 600 ~/.vnc/passwd ---> Using cache ---> af74e65141be Step 13/16 : RUN printf '\n\n\n\n%s\n%s\n\n\n\n' '===========VNC_PASSWORD========== ' "$(<vncpasswd_file)" ---> Using cache ---> 93b5440515eb Step 14/16 : WORKDIR /home/arch/OSX-KVM ---> Using cache ---> 6aca647168a0 Step 15/16 : USER arch ---> Using cache ---> 1ab163ce8287 Step 16/16 : CMD ./OpenCore-Boot_custom.sh ---> Using cache ---> fca260b8ecbf Successfully built fca260b8ecbf Successfully tagged local/docker-osx:latest me@mymac vnc-version % docker run --privileged -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix local/docker-osx ./OpenCore-Boot.sh 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 ``` I did a `brew install qemu` but I don't think that's my issue? I also tried: ``` me@mymac vnc-version % docker run local/docker-osx Can't find file /home/arch/.vnc/24a99c353255:99.pid You'll have to kill the Xvnc process manually xauth: file /home/arch/.Xauthority does not exist New '24a99c353255:99 (arch)' desktop is 24a99c353255:99 Creating default config /home/arch/.vnc/config Starting applications specified in /home/arch/.vnc/xstartup Log file is /home/arch/.vnc/24a99c353255:99.log Could not access KVM kernel module: No such file or directory qemu-system-x86_64: failed to initialize kvm: No such file or directory ```

adam commented

2025-12-29 05:19:24 +01:00

@sickcodes commented on GitHub (Jun 14, 2020):

Noted, if anyone has had success with this issue, would be great to hear :) I will try test it later today

@sickcodes commented on GitHub (Jun 14, 2020): Noted, if anyone has had success with this issue, would be great to hear :) I will try test it later today

adam commented

2025-12-29 05:19:27 +01:00

@cmosetick commented on GitHub (Jun 16, 2020):

echo $DISPLAY
/private/tmp/com.apple.launchd.lWN3QYe0Ym/org.macosforge.xquartz:0

I get a similar output on OS X 10.15.5.
docker for mac desktop version 2.3.0.3
docker version 19.03.8

docker run --privileged -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix cmosetick/docker-osx:vnc-version
ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519

Can't find file /home/arch/.vnc/3a2312c0264b:99.pid
You'll have to kill the Xvnc process manually


Warning: 3a2312c0264b:99 is taken because of /tmp/.X11-unix/X99
Remove this file if there is no X server 3a2312c0264b:99
A VNC server is already running as :99
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

@cmosetick commented on GitHub (Jun 16, 2020): ``` echo $DISPLAY /private/tmp/com.apple.launchd.lWN3QYe0Ym/org.macosforge.xquartz:0 ``` I get a similar output on OS X 10.15.5. docker for mac desktop version `2.3.0.3` docker version `19.03.8` ``` docker run --privileged -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix cmosetick/docker-osx:vnc-version ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519 Can't find file /home/arch/.vnc/3a2312c0264b:99.pid You'll have to kill the Xvnc process manually Warning: 3a2312c0264b:99 is taken because of /tmp/.X11-unix/X99 Remove this file if there is no X server 3a2312c0264b:99 A VNC server is already running as :99 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 ```

adam commented

2025-12-29 05:19:28 +01:00

@sickcodes commented on GitHub (Jun 20, 2020):

Try

-e DISPLAY=:0

@sickcodes commented on GitHub (Jun 20, 2020): Try `-e DISPLAY=:0`

adam commented

2025-12-29 05:19:28 +01:00

@sickcodes commented on GitHub (Jun 20, 2020):

But that’s for the X11 version. Don’t use display for the VNC version. Use the instructions in the top of the Dockerfile for VNC


# Build:
#
#       # write down the password at the end
#       docker build -t docker-osx-vnc .
# 
# Run:
#       
#       docker run -p 8888:5999 -p 50922:10022 -d --privileged docker-osx-vnc:latest
#
#
# Connect locally (safe):
#
#       VNC Host:     localhost:8888

@sickcodes commented on GitHub (Jun 20, 2020): But that’s for the X11 version. Don’t use display for the VNC version. Use the instructions in the top of the Dockerfile for VNC ``` # Build: # # # write down the password at the end # docker build -t docker-osx-vnc . # # Run: # # docker run -p 8888:5999 -p 50922:10022 -d --privileged docker-osx-vnc:latest # # # Connect locally (safe): # # VNC Host: localhost:8888 ```

adam commented

2025-12-29 05:19:28 +01:00

@shuangwei-Ye commented on GitHub (Jun 28, 2020):

emmmmm..... i want to know the result. i have this same issue.

@shuangwei-Ye commented on GitHub (Jun 28, 2020): emmmmm..... i want to know the result. i have this same issue.

adam commented

2025-12-29 05:19:29 +01:00

@shuangwei-Ye commented on GitHub (Jun 28, 2020):

ARCH

but...are these linux version? ARCH \centos \ UBUNTU. how to use this instruction in Mac os ？

@shuangwei-Ye commented on GitHub (Jun 28, 2020): > ARCH but...are these linux version? ARCH \centos \ UBUNTU. how to use this instruction in Mac os ？

adam commented

2025-12-29 05:19:29 +01:00

@sickcodes commented on GitHub (Jul 4, 2020):

ARCH

but...are these linux version? ARCH \centos \ UBUNTU. how to use this instruction in Mac os ？

This is a Dockerfile, so you'd need Docker first: https://docs.docker.com/engine/install/

@sickcodes commented on GitHub (Jul 4, 2020): > > ARCH > > but...are these linux version? ARCH \centos \ UBUNTU. how to use this instruction in Mac os ？ This is a Dockerfile, so you'd need Docker first: https://docs.docker.com/engine/install/

adam commented

2025-12-29 05:19:29 +01:00

@shuangwei-Ye commented on GitHub (Jul 14, 2020):

ARCH

but...are these linux version? ARCH \centos \ UBUNTU. how to use this instruction in Mac os ？

This is a Dockerfile, so you'd need Docker first: https://docs.docker.com/engine/install/

I've already downloaded Docker Desktop for Mac (macOS), then run this project.

now I got the same result as tibbon

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

I wonder if Mac can run a Docker-OSX～

thanks

@shuangwei-Ye commented on GitHub (Jul 14, 2020): > > > ARCH > > > > > > but...are these linux version? ARCH \centos \ UBUNTU. how to use this instruction in Mac os ？ > > This is a Dockerfile, so you'd need Docker first: https://docs.docker.com/engine/install/ I've already downloaded Docker Desktop for Mac (macOS), then run this project. now I got the same result as tibbon ``` 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 ``` I wonder if Mac can run a Docker-OSX～ thanks

adam commented

2025-12-29 05:19:29 +01:00

@drewdrew21b commented on GitHub (Oct 1, 2020):

I was able to build using docker-osx:vnc-version and launch with the suggested options in the script (docker run -p 8888:5999 -p 50922:10022 -d --privileged ).

I am seeing the following when logging in via macOS built in Screen Sharing (and Real VNC) using the randomly generated VNC password:

When I try to click on the Recovery Drive to install macOS, I get the following kernel panic:

I am using Portainer (1.24.1) to manage Docker Desktop (2.4.0.0 build 48506) with brew QEMU (5.1.0) on MacOS 10.15.7.

This looks like it's somewhat working, up until the kernel panic's. Is there anything else I can grab to debug this?

@drewdrew21b commented on GitHub (Oct 1, 2020): I was able to build using [docker-osx:vnc-version](https://github.com/sickcodes/Docker-OSX/tree/master/vnc-version) and launch with the suggested options in the script (docker run -p 8888:5999 -p 50922:10022 -d --privileged <dockerBuildImageValue>). I am seeing the following when logging in via macOS built in Screen Sharing (and Real VNC) using the randomly generated VNC password: ![Screen Shot 2020-10-01 at 3 09 23 PM](https://user-images.githubusercontent.com/63080025/94863866-5b17ef00-03f8-11eb-9d02-9f8c5de03324.png) When I try to click on the Recovery Drive to install macOS, I get the following kernel panic: ![Screen Shot 2020-10-01 at 3 15 08 PM](https://user-images.githubusercontent.com/63080025/94864484-47b95380-03f9-11eb-854a-a5faeeec3052.png) I am using Portainer (1.24.1) to manage Docker Desktop (2.4.0.0 build 48506) with brew QEMU (5.1.0) on MacOS 10.15.7. This looks like it's somewhat working, up until the kernel panic's. Is there anything else I can grab to debug this?

adam commented

2025-12-29 05:19:30 +01:00

@sickcodes commented on GitHub (Oct 2, 2020):

@drewdrew21b thats pretty close!

I'm not sure, I will try in a Docker-OSX to replicate this tomorrow so we can get the true full circle: OSX in OSX

You can try building the main image
And then using that image in the VNC script (change FROM to your build)

@sickcodes commented on GitHub (Oct 2, 2020): @drewdrew21b thats pretty close! I'm not sure, I will try in a Docker-OSX to replicate this tomorrow so we can get the true full circle: OSX in OSX You can try building the main image And then using that image in the VNC script (change FROM to your build)

adam commented

2025-12-29 05:19:30 +01:00

@drewdrew21b commented on GitHub (Oct 2, 2020):

@sickcodes I tried to create a build on my MacBook Pro and Mac Mini and am getting what appears to be the same crash in both instances from macOS recovery when booting the recovery kernel.

@drewdrew21b commented on GitHub (Oct 2, 2020): @sickcodes I tried to create a build on my MacBook Pro and Mac Mini and am getting what appears to be the same crash in both instances from macOS recovery when booting the recovery kernel.

adam commented

2025-12-29 05:19:30 +01:00

@majest commented on GitHub (Oct 14, 2020):

Any updates on that? The OSX in OSX feature would be really useful.

@majest commented on GitHub (Oct 14, 2020): Any updates on that? The OSX in OSX feature would be really useful.

adam commented

2025-12-29 05:19:31 +01:00

@sickcodes commented on GitHub (Oct 15, 2020):

Unfortunately I can't test it

@sickcodes commented on GitHub (Oct 15, 2020): Unfortunately I can't test it

adam commented

2025-12-29 05:19:31 +01:00

@gitpushdashf commented on GitHub (Oct 20, 2020):

Same issue for me. Thanks for making this, though!

@gitpushdashf commented on GitHub (Oct 20, 2020): Same issue for me. Thanks for making this, though! ![Screen Shot 2020-10-20 at 12 43 26 PM](https://user-images.githubusercontent.com/66637483/96630160-da029800-12d1-11eb-9d41-f08021623858.png)

adam commented

2025-12-29 05:19:31 +01:00

@adamwolf commented on GitHub (Apr 5, 2021):

I get the same issue as gitpushdashf. (Is there a common emoji reaction for "this happens to me, too"?)

@adamwolf commented on GitHub (Apr 5, 2021): I get the same issue as gitpushdashf. (Is there a common emoji reaction for "this happens to me, too"?)

adam commented

2025-12-29 05:19:32 +01:00

@ghost commented on GitHub (Apr 7, 2021):

MacOSX doesn't have KVM, KVM is Linux only, the project relies on KVM, therefore it can't run on MacOSX

@ghost commented on GitHub (Apr 7, 2021): MacOSX doesn't have KVM, KVM is Linux only, the project relies on KVM, therefore it can't run on MacOSX

adam commented

2025-12-29 05:19:32 +01:00

@sickcodes commented on GitHub (Apr 18, 2021):

You can run without it KVM on any platform.

I did it before, using OSX-KVM on a raspberry Pi.

A few command changes are needed I'll try and find the bash history. I would've saved it.

Also, don't when I did it on a RPI, I never got past the Apple Logo. Maybe because the SD card is exponentially slower than an SSD.

Don't forget the disk is large and needs more a bit of ram.

The Dockerfile is not multiarch.
You can tell because we have some x86 patches.

It's 100% possible.

@sickcodes commented on GitHub (Apr 18, 2021): You can run without it KVM on any platform. I did it before, using OSX-KVM on a raspberry Pi. A few command changes are needed I'll try and find the bash history. I would've saved it. Also, don't when I did it on a RPI, I never got past the Apple Logo. Maybe because the SD card is exponentially slower than an SSD. Don't forget the disk is large and needs more a bit of ram. **The Dockerfile is not multiarch.** You can tell because we have some x86 patches. It's 100% possible.

adam commented

2025-12-29 05:19:32 +01:00

@deepio commented on GitHub (Apr 18, 2021):

I really wanted to make matryoshka happen, but for now it seems I need to stick with https://github.com/myspaghetti/macos-virtualbox when on a MacOS host and Docker-OSX when on *nix.

This is how I ran it and got as far as the others:

From the security tab in the XQuartz preferences, make sure Allow connections from network clients is enabled. Restart XQuartz after enabling it if it wasn't.

xhost +localhost
docker run --privileged -e DISPLAY=host.docker.internal:0 sickcodes/docker-osx

@deepio commented on GitHub (Apr 18, 2021): I really wanted to make matryoshka happen, but for now it seems I need to stick with https://github.com/myspaghetti/macos-virtualbox when on a MacOS host and Docker-OSX when on *nix. This is how I ran it and got as far as the others: - From the security tab in the XQuartz preferences, make sure Allow connections from network clients is enabled. Restart XQuartz after enabling it if it wasn't. ```bash xhost +localhost docker run --privileged -e DISPLAY=host.docker.internal:0 sickcodes/docker-osx ```

adam commented

2025-12-29 05:19:32 +01:00

@lbdl commented on GitHub (Apr 27, 2021):

seems I have the same issue as everyone else, can get the container to start using the same as @deepio has posted however the startup kernel panics in the same manner.
Steps install XQuartz -> allow connections from network clients.

xhost +localhost
docker run --privileged -e DISPLAY=host.docker.internal:0 sickcodes/docker-osx

@lbdl commented on GitHub (Apr 27, 2021): seems I have the same issue as everyone else, can get the container to start using the same as @deepio has posted however the startup kernel panics in the same manner. Steps install XQuartz -> allow connections from network clients. ``` xhost +localhost docker run --privileged -e DISPLAY=host.docker.internal:0 sickcodes/docker-osx ``` <img width="620" alt="Screenshot 2021-04-27 at 18 36 19" src="https://user-images.githubusercontent.com/554064/116286844-9c526080-a787-11eb-8081-ebc7fd3b55c9.png">

adam commented

2025-12-29 05:19:32 +01:00