Docker-OSX

[GreenEyedMonster]

Hey everyone,

 

I found this amazing docker https://github.com/sickcodes/Docker-OSX and I would love to use it on my Unraid server.  I would like to keep all my jailbreaking stuff in it.  (Don't like having that software on my macbook.)  Does anyone know how to install it correctly?  

I get this error: 

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

Thanks!

[bastl]

@GreenEyedMonster Use the following Docker which does basically the same. Installing MacOS in a VM. Watch SpaceInvaders video and you should be good to go

 

 

 

[GreenEyedMonster]

@bastl  From my understanding this is a bit different since it is already running in the Docker as a reachable through VNC OSX install.   I don't know what variables etc... to give it so that I can VNC into it.  I'm stuck at KVM values.

[GreenEyedMonster]

Anyone else want to take a stab at it??

[Hugo.X]

They just launched the offcial version and I am having the same problem. So does anyone did sucessfully in unRaid docker UI?

[Ford Prefect]

never used it, but the main hint, I think is this: 

Special thanks to @kholia for maintaining the upstream project, which Docker-OSX is built on top of: OSX-KVM.

 

Looks like the Docker is using something like nested Virtualisation inside, by enabling access by "--device /dev/kvm", so OSX can run inside the container.

 

The readme @ OSX-KVM states:

Installation Preparation
KVM may need the following tweak on the host machine to work.

echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs
To make this change permanent, you may use the following command.

sudo cp kvm.conf /etc/modprobe.d/kvm.conf  # for intel boxes

 

...feels like a not-so-minor change in the unraid config, when mangle with KVM on the host side, I think.

[lnxd]

Oh my god.. Not only is this container amazing, I got it to work! ☺️

 

For anyone interested, it's not too difficult. I had to set some permissions, clone the source and build the vnc-version but it works.

 

Edited April 7, 2021 by lnxd

[Chamzamzoo]

Any thoughts as to what would be better performance for a regular use MacOSX system, the VM route or this docker?

[Irithor]

On 4/7/2021 at 10:18 PM, lnxd said:

Oh my god.. Not only is this container amazing, I got it to work! ☺️

 

For anyone interested, it's not too difficult. I had to set some permissions, clone the source and build the vnc-version but it works.

 

Trying to get it running now, any chance you'd care to elaborate on the process? Thanks in advance!

[c0d3m0nk3y]

On 4/7/2021 at 8:18 AM, lnxd said:

Oh my god.. Not only is this container amazing, I got it to work! ☺️

 

For anyone interested, it's not too difficult. I had to set some permissions, clone the source and build the vnc-version but it works.

 

Can you give us more details please? I have MacInABox setup as an AirMessage server but hoping this container will be a bit lighter weight

[darthcircuit]

I'm still working to get mine set up, but the vnc container does run and stays running unlike the standard one.

Here's what I did:

 

open the terminal on your unraid machine either through the web or ssh.
 

#entirely optional.. i just wanted an easy place to dump the dockerfile temporarily
mkdir /var/tmp/docker-osx
cd /var/tmp/docker-osx

wget https://raw.githubusercontent.com/sickcodes/Docker-OSX/master/vnc-version/Dockerfile

docker build -t docker-osx-vnc .
docker run --device /dev/kvm --device /dev/snd -p 8888:5999 -p 50922:10022 -d --privileged docker-osx-vnc:latest

 

that should get it to show up in your containers list in unraid. I didn't have to change any default settings or permissions. Just r

 

After it starts running, you will be shown a vnc password in the terminal. Copy than and then you can connect to it with VNC on port 8888. I just used RealVNC viewer to connect. Works a treat.

I'm looking at adding NoVNC support to mine later, but that will a problem for future darthcircuit to worry about.

 

 

Edited April 22, 2022 by darthcircuit

[Madman2012]

Looks like I got it to install with your excellent directions via the terminal - but it appears as an orphaned image in the docker tab. Can you explain how I may resolve this? Thanks in advance! 

[juan11perez]

@Madman2012

That's because the docker run command did not included  a name variable ( for example -name catalina). So docker assigns a random name.

 

To rename it type in terminal docker rename <current_name> <new_name>

[Madman2012]

@juan11perezThank you!! How do we get this in the CA store? Would be great for more people to use it to tinker.

[Abhi]

This are the commands I use to have ventura and to get iMessage working. I left SERIAL, BOARD_SERIAL, UUID, and MAC_ADDRESS empty as thats specific to each user. Check this out to get those generated. 

 

I didn't use the vnc version mentioned in an earlier post here. Idk what difference it makes, but everything works fine for me. VNC included. 

mkdir /var/tmp/docker-osx
cd /var/tmp/docker-osx

wget https://raw.githubusercontent.com/sickcodes/Docker-OSX/master/Dockerfile

docker build -t docker-osx --build-arg VERSION=13.0 --build-arg SIZE=200G .

Then run this after the docker build

docker run -i \
	--device /dev/kvm \
    --device /dev/snd \
	--name='Docker-OSX' \
	-d --privileged \
	-p 50922:10022 \
	-p 8888:5999 \
	-v /tmp/.X11-unix:/tmp/.X11-unix \
	-e "DISPLAY=${DISPLAY:-:0.0}" \
	-e RAM=6 \
	-e NETWORKING=vmxnet3 \
    -e EXTRA="-display none -vnc 0.0.0.0:99,password=on" \
	-e MASTER_PLIST_URL=https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist \
    -e GENERATE_SPECIFIC=true \
    -e DEVICE_MODEL="iMac20,2" \
    -e SERIAL="" \
    -e BOARD_SERIAL="" \
    -e UUID="" \
    -e MAC_ADDRESS="" \
	sickcodes/docker-osx:ventura

 

I was wondering if anyone can get ^ this translated into a dockerMan xml to be used on community apps?

Edited February 14, 2023 by Abhi

[Fffrank]

I wasn't able to get the macosinabox to ever work (not sure if it's because I have an X5660 machine?)  But I did get this dockerized version to work relatively easily.  I'm curious, though -- does anyone know how we can build this to its own image or disk?  It adds at least 20gb to my docker.img file and doesn't seem to survive blowing that up and starting over once you get the image installed?

[slipperyfart]

On 2/14/2023 at 11:53 AM, Abhi said:

This are the commands I use to have ventura and to get iMessage working. I left SERIAL, BOARD_SERIAL, UUID, and MAC_ADDRESS empty as thats specific to each user. Check this out to get those generated. 

 

I didn't use the vnc version mentioned in an earlier post here. Idk what difference it makes, but everything works fine for me. VNC included. 

mkdir /var/tmp/docker-osx
cd /var/tmp/docker-osx

wget https://raw.githubusercontent.com/sickcodes/Docker-OSX/master/Dockerfile

docker build -t docker-osx --build-arg VERSION=13.0 --build-arg SIZE=200G .

Then run this after the docker build

docker run -i \
	--device /dev/kvm \
    --device /dev/snd \
	--name='Docker-OSX' \
	-d --privileged \
	-p 50922:10022 \
	-p 8888:5999 \
	-v /tmp/.X11-unix:/tmp/.X11-unix \
	-e "DISPLAY=${DISPLAY:-:0.0}" \
	-e RAM=6 \
	-e NETWORKING=vmxnet3 \
    -e EXTRA="-display none -vnc 0.0.0.0:99,password=on" \
	-e MASTER_PLIST_URL=https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist \
    -e GENERATE_SPECIFIC=true \
    -e DEVICE_MODEL="iMac20,2" \
    -e SERIAL="" \
    -e BOARD_SERIAL="" \
    -e UUID="" \
    -e MAC_ADDRESS="" \
	sickcodes/docker-osx:ventura

 

I was wondering if anyone can get ^ this translated into a dockerMan xml to be used on community apps?

I was able to get it working using these commands. The setup was pretty seamless, the only issue that I'm running into is that this drastically increases the size of the docker.img file. I know that there is a way to add a volume that points to a different location in the shares on unraid like /mnt/user/domains or somewhere else but I'm not entirely sure how to do it myself. Has anyone figured out a way to do this so that the dock.img file doesn't fill up so much because of this VM?