You've already forked Docker-OSX
mirror of
https://github.com/sickcodes/Docker-OSX.git
synced 2025-07-03 11:13:32 -05:00
fix helm initial disk creation process and add installation instructions
This commit is contained in:
@ -11,7 +11,7 @@ image:
|
||||
# Please note, this must be a directory name within `/system_image` mounted at the bottom in extraVolumeMounts
|
||||
serverName: server
|
||||
|
||||
# SMBIOS settings (please be sure to update these as to use something unique for iServices)
|
||||
# SMBIOS settings
|
||||
configPlist:
|
||||
SystemProductName: iMacPro1,1
|
||||
MLB: D25338500GUF8YLJA
|
||||
@ -19,8 +19,24 @@ configPlist:
|
||||
SystemUUID: 139C94D6-A533-47D2-874F-D365BFD8B047
|
||||
|
||||
# This defines QEMU and virtlo parameters
|
||||
#
|
||||
# Note:
|
||||
# *) Increase downloadDelay if the pod gets killed for readiness/liveliness check. The first time the pod is started,
|
||||
# it will download the BaseSystem image and create a data partition to install the OS. If this value is really long,
|
||||
# the pod will take very long to allow VNC connections if it is rebooted/killed.
|
||||
# *) Big Sur (11.X) is currently broken, as it seems to need the BaseSystem extracted from the InstallAssistant.pkg file it downloads
|
||||
# *) GPU support is considered broken still, but WIP
|
||||
#
|
||||
qemu:
|
||||
cpu: Penryn,vendor=GenuineIntel,+hypervisor,+invtsc,kvm=on,+fma,+avx,+avx2,+aes,+ssse3,+sse4_2,+popcnt,+sse4a,+bmi1,+bmi2
|
||||
cpu: Penryn,vendor=GenuineIntel,+hypervisor,+invtsc,kvm=on,+fma,+avx,+avx2,+aes,+ssse3,+sse4_2,+popcnt,+sse4a,+bmi1,+bmi2
|
||||
softwareGpu: vmware
|
||||
gpu:
|
||||
# if disabled, will rely on softwareGpu instead
|
||||
enabled: false
|
||||
hardwareId: '03:00'
|
||||
systemInstaller:
|
||||
version: 10.15.7
|
||||
downloadDelay: 300
|
||||
diskSize: 128G
|
||||
audio:
|
||||
enabled: true
|
||||
@ -55,7 +71,7 @@ ingress:
|
||||
# hosts:
|
||||
# - chart-example.local
|
||||
|
||||
# Note: seems that host needs around x5 the cpu and x8 memory limits allocated to MacOS
|
||||
# Note: seems that host needs around x5 the cpu and x9 memory limits allocated to MacOS
|
||||
# when under load. This may be due to my personal hardware or inefficencies such as
|
||||
# software GPU rendering. Otherwise the pod will be killed due to OOMing.
|
||||
#
|
||||
@ -64,7 +80,7 @@ ingress:
|
||||
resources:
|
||||
limits:
|
||||
cpu: 10
|
||||
memory: 33554Mi
|
||||
memory: 36864Mi
|
||||
requests:
|
||||
cpu: 2
|
||||
memory: 4096Mi
|
||||
|
Reference in New Issue
Block a user