Open Santosl2 opened 2 months ago
I get this same issue, however, I have never managed to get this to boot even with default docker compose.
up
For what it's worth I'm able to see more than 1 CPU core on my end (at least, according to "System Report" within Sonoma):
System Report
"About This Mac"
Host system
Docker Compose Config
image: dockurr/macos
cap_add:
- NET_ADMIN
devices:
- /dev/kvm
environment:
CPU_CORES: "16"
RAM_SIZE: "8G"
VERSION: "sonoma"
ports:
- 8006:8006
restart: unless-stopped
stop_grace_period: 2m
volumes:
- type: bind
source: /data/osx-storage
target: /storage
For what it's worth I'm able to see more than 1 CPU core on my end (at least, according to "System Report" within Sonoma):
System Report
"About This Mac"
Host system
- CPU: AMD Ryzen 9 5950X 16-Core
- Mem: 64G
- OS: Ubuntu 22.04.4 LTS
Docker Compose Config
image: dockurr/macos cap_add: - NET_ADMIN devices: - /dev/kvm environment: CPU_CORES: "16" RAM_SIZE: "8G" VERSION: "sonoma" ports: - 8006:8006 restart: unless-stopped stop_grace_period: 2m volumes: - type: bind source: /data/osx-storage target: /storage
Didn't work here... I got the same error:
Are you using nested virtualization by any chance?
Are you using nested virtualization by any chance?
How can i check this?
@Santosl2 If you are running your OS (and the container) inside a Virtual Machine or bare metal.
@Santosl2 If you are running your OS (and the container) inside a Virtual Machine or bare metal.
Ooo, no
Is your question not already answered in the FAQ?
Is this a general question and not a technical issue?
Question
So i'm trying run on Linux, my PC config is:
However, when i try to use more than one CPU core, macOS doesn't boot and gets stuck on this screen:
_When i change
CPU_CORES
to ONE works fine_My docker.compose.yml