Repository files navigation

OSX (macOS) inside a Docker container.

• KVM acceleration
• Web-based viewer
• Automatic download

Via Docker Compose:

services:macos:image:dockurr/macoscontainer_name:macosenvironment:VERSION:"13"devices:      -/dev/kvm      -/dev/net/tuncap_add:      -NET_ADMINports:      -8006:8006      -5900:5900/tcp      -5900:5900/udpvolumes:      -./macos:/storagerestart:alwaysstop_grace_period:2m

Via Docker CLI:

docker run -it --rm --name macos -p 8006:8006 --device=/dev/kvm --device=/dev/net/tun --cap-add NET_ADMIN -v${PWD:-.}/macos:/storage --stop-timeout 120 dockurr/macos

Via Kubernetes:

kubectl apply -f https://raw.githubusercontent.com/dockur/macos/refs/heads/master/kubernetes.yml

Very simple! These are the steps:

• Start the container and connect toport 8006 using your web browser.

• ChooseDisk Utility and then select the largestApple Inc. VirtIO Block Media disk.

• Click theErase button to format the disk to APFS, and give it any name you like.

• Close the current window and proceed the installation by clickingReinstall macOS.

• When prompted where you want to install it, select the disk you created previously.

• After all files are copied, select your region, language, and account settings.

Enjoy your brand new machine, and don't forget to star this repo!

By default, macOS 13 (Ventura) will be installed, but you can add theVERSION environment variable in order to specify an alternative:

environment:VERSION:"13"

Select from the values below:

To change the storage location, include the following bind mount in your compose file:

volumes:  -./macos:/storage

Replace the example path./macos with the desired storage folder or named volume.

To expand the default size of 64 GB, add theDISK_SIZE setting to your compose file and set it to your preferred capacity:

environment:DISK_SIZE:"256G"

By default, the container will be allowed to use a maximum of 2 CPU cores and 4 GB of RAM.

If you want to adjust this, you can specify the desired amount using the following environment variables:

environment:RAM_SIZE:"8G"CPU_CORES:"4"

By default, the container uses bridge networking, which shares the IP address with the host.

If you want to assign an individual IP address to the container, you can create a macvlan network as follows:

docker network create -d macvlan \    --subnet=192.168.0.0/24 \    --gateway=192.168.0.1 \    --ip-range=192.168.0.100/28 \    -o parent=eth0 vlan

Be sure to modify these values to match your local subnet.

Once you have created the network, change your compose file to look as follows:

services:macos:container_name:macos..<snip>..networks:vlan:ipv4_address:192.168.0.100networks:vlan:external:true

An added benefit of this approach is that you won't have to perform any port mapping anymore, since all ports will be exposed by default.

After configuring the container formacvlan, it is possible for macOS to become part of your home network by requesting an IP from your router, just like your other devices.

To enable this mode, in which the container and macOS will have separate IP addresses, add the following lines to your compose file:

environment:DHCP:"Y"devices:  -/dev/vhost-netdevice_cgroup_rules:  -'c *:* rwm'

To pass-through a USB device, first lookup its vendor and product id via thelsusb command, then add them to your compose file like this:

environment:ARGUMENTS:"-device usb-host,vendorid=0x1234,productid=0x1234"devices:  -/dev/bus/usb

To share files with the host, add the following volume to your compose file:

volumes:  -./example:/shared

Then start macOS and execute the following command:

sudo -S mount_9p shared

In Finder’s menu bar, click on “Go – Computer” to access this shared folder, it will show the contents of./example.

Only Linux and Windows 11 support KVM virtualization, macOS and Windows 10 do not unfortunately.

You can run the following commands in Linux to check your system:

sudo apt install cpu-checkersudo kvm-ok

If you receive an error fromkvm-ok indicating that KVM cannot be used, please check whether:

• the virtualization extensions (Intel VT-x orAMD SVM) are enabled in your BIOS.

• you enabled "nested virtualization" if you are running the container inside a virtual machine.

• you are not using a cloud provider, as most of them do not allow nested virtualization for their VPS's.

If you do not receive any error fromkvm-ok but the container still complains about KVM, please check whether:

• you are not using "Docker Desktop for Linux" as it does not support KVM, instead make use of Docker Engine directly.

• it could help to addprivileged: true to your compose file (orsudo to yourdocker run command), to rule out any permission issue.

You can usedockur/windows for that. It shares many of the same features, and even has completely automatic installation.

You can useqemus/qemu in that case.

Yes, this project contains only open-source code and does not distribute any copyrighted material. Neither does it try to circumvent any copyright protection measures. So under all applicable laws, this project will be considered legal.

However, by installing Apple's macOS, you must accept their end-user license agreement, which does not permit installation on non-official hardware. So only run this container on hardware sold by Apple, as any other use will be a violation of their terms and conditions.

Special thanks toseitenca, this project would not exist without her invaluable work.

Only run this container on Apple hardware, any other use is not permitted by their EULA. The product names, logos, brands, and other trademarks referred to within this project are the property of their respective trademark holders. This project is not affiliated, sponsored, or endorsed by Apple Inc.