mirror of
https://github.com/sickcodes/Docker-OSX.git
synced 2024-12-27 18:06:07 +00:00
.. | ||
templates | ||
.DS_Store | ||
Chart.yaml | ||
README.md | ||
values.yaml |
docker-osx
Information
This installs docker-osx
in Kubernetes.
Features
What works
- Setting cpu/memory options
- Setting VNC password
- Persistance
- Setting SMBIOS
- QEMU/virtio cpu/software gpu changes
- Toggling Audio
- Additional port forwarding
- Kubernetes resource requests/limits
- Defining version of macOS to install
- Defining install partition size
What doesn't/isn't defined
- Defining a different version of macOS
- Additional QEMU parameters
- GPU support
Requirements
*) Install host machine requirements
*) Ensure you are running QEMU 5.X
*) Kubernetes
*) Helm v2
*) sickcodes/docker-osx-vnc
Docker image
Build sickcodes/docker-osx-vnc
-
Go back to the root directory
-
Build docker image
docker build \ -t sickcodes/docker-osx-vnc:latest \ -f vnc-version/Dockerfile .
Do not worry about passing CPU
, RAM
, etc as they are handled in values.yaml
now.
Installation
In values.yaml
..
- Set a unique password for
vnc.password
. - Re-generate SMBIOS
configPlist.MLB
,configPlist.SystemSerialNumber
, andconfigPlist.SystemUUID
for iServices to work. - Update
serverName
to reflect the unique name (in the case more than one deployment is required). - Configure
qemu.systemInstaller.downloadDelay
(in a period of seconds) that reflects how long your internet connection will download around 500MB (BaseSystem.dmg) + uncompress the file (which took about the same time for me to download on a 1gig internet connection). - Set
service.ip
to reflect an IP address of your choice, or use ingress. - Update
extraVolumes.hostPath.path
to something useful for you.
Afterwards..
- Launch your VNC viewer of choice and connect to the IP/hostname you defined + the port
8888
with the password specified forvnc.password
. - Install macOS like usual.
Please note, after you have installed macOS feel free to set qemu.systemInstaller.downloadDelay
to nothing, as BaseSystem.dmg will be stored in the path defined for extraVolumes.hostPath.path
Resources
Please note, resource limits may vary based on hardware. The ones currently defined are ones that worked for me personally.