sickcodes / Docker-OSX

Run macOS VM in a Docker! Run near native OSX-KVM in Docker! X11 Forwarding! CI/CD for OS X Security Research! Docker mac Containers.
https://hub.docker.com/r/sickcodes/docker-osx
GNU General Public License v3.0
36.13k stars 1.78k forks source link

Ventura not working #658

Open FuadFox opened 1 year ago

FuadFox commented 1 year ago

Hello I am trying to run

docker run -it \
    --device /dev/kvm \
    -p 50922:10022 \
    -v /tmp/.X11-unix:/tmp/.X11-unix \
    -e "DISPLAY=${DISPLAY:-:0.0}" \
    -e GENERATE_UNIQUE=true \
    -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \
    sickcodes/docker-osx:ventura

# docker build -t docker-osx --build-arg SHORTNAME=ventura .

But once it runs I don't see a disk utility unlike others like catalina (Catalina worked fine, but I need a higher version to build IOS16 apps) it only shows two options. see the picture below.

Screenshot from 2023-05-05 15-49-38

and once I choose macOs Base System it shows this. image

nothings more it just hangs there.

and if I choose UEFI Shell shows this and hangs.

image

how can I access the installer please help.

Linux fuad 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
:0
1
PRETTY_NAME="Ubuntu 23.04"
NAME="Ubuntu"
VERSION_CODENAME=lunar
UBUNTU_CODENAME=lunar
Filesystem      Size  Used Avail Use% Mounted on
/dev/nvme0n1p2  457G  208G  227G  48% /
QEMU emulator version 7.2.0 (Debian 1:7.2+dfsg-5ubuntu2)
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developers
Command 'libvirtd' not found, but can be installed with:
sudo apt install libvirt-daemon
               total        used        free      shared  buff/cache   available
Mem:            13Gi       3.3Gi       343Mi        63Mi        10Gi        10Gi
Swap:          2.0Gi       1.4Gi       614Mi
8
8
crw-rw----+ 1 root kvm 10, 232 May  5 15:25 /dev/kvm
total 32K
drwxrwxrwt  2 root root 4.0K May  5 01:55 .
drwxrwxrwt 23 root root  24K May  5 15:46 ..
srwxrwxrwx  1 fuad fuad    0 May  5 01:55 X0
root        4008  0.6  0.3 1908608 50060 ?       Ssl  01:55   5:12 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
fuad     2526929  0.0  0.0   9300  2304 pts/4    S+   15:46   0:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn --exclude-dir=.idea --exclude-dir=.tox dockerd
c74ee1e18ec4   sickcodes/docker-osx:ventura   "/bin/bash -c 'sudo …"   21 minutes ago   Up 21 minutes   0.0.0.0:50924->10022/tcp, :::50924->10022/tcp   goofy_tharp
kvm:x:109:
docker:x:999:fuad
FuadFox commented 1 year ago

@sickcodes can you help with this please

PTAHume commented 1 year ago

hi could you try the following and see if it works for you

could you beforehand ensure you have run

wsl --update
wsl
sudo su
<<enter your password for the destro>>
sudo apt -y install libvirtd
sudo apt -y install bridge-utils cpu-checker libvirt-clients libvirt-daemon qemu qemu-kvm
sudo apt-get update && sudo apt-get upgrade -y && sudo apt-get full-upgrade

then run the

docker run -it \ --privileged \
    --device /dev/kvm \
    -p 50922:10022 \
    -v /tmp/.X11-unix:/tmp/.X11-unix \
    -e "DISPLAY=${DISPLAY:-:0.0}" \
    -e GENERATE_UNIQUE=true \
    -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \
    sickcodes/docker-osx:ventura

i hope this helps ?

arjanflac commented 1 year ago

Format drive to mac OS extended (Journaled) instead of APFS Long time issue.

Please document or fix

https://github.com/sickcodes/Docker-OSX/issues/511 https://github.com/sickcodes/Docker-OSX/issues/571

https://github.com/sickcodes/Docker-OSX/issues/571#issuecomment-1427754105

richardbowman commented 1 year ago

The issue occurs before formatting the disk - after selecting from the boot loader, the image hangs just as @FuadFox mentioned. Unfortunately with XCode now requiring Ventura, my whole plan to use IOS Simulator on my Linux box is on pause I guess :-)

richardbowman commented 1 year ago

Hmm the exact thing is also happening for me with Monterey, even though Catalina worked fine.

image

programmrz commented 1 year ago

What CPU are you running on your Linux box? Ventura requires AVX2 support.

danrossi commented 1 year ago

I'm struggling to get Ventura working on AMD. Ryzen supports AVX2. Its booting into recovery. Vmware went into boot loops. ITs needed for IOS 16.4 dev

richardbowman commented 1 year ago

I'm on an AMD Ryzen 7 3700. Checking for AVX2, cpuinfo shows it.

tejas-luthra commented 1 year ago

I am on AMD Ryzen 7 5800H and I am also experiencing the same issue. I can confirm that my CPU does support avx.

DoubleMalt commented 1 year ago

Format drive to mac OS extended (Journaled) instead of APFS Long time issue.

Please document or fix

511 #571

#571 (comment)

This doesn't work for me either.

/edit

Addition: Also installing Monterey on HFS and upgrading to Ventura doesn't work. Ends in a boot loop. My System is a Xeon E5-1650 with axv2 support

danrossi commented 1 year ago

I think they have well and truely broken VM on Windows AMD specifically. Ryzen has the required support. VMWare works up to Ventura but simulator crashes. Simulator doesn't load in Docker. They make you require Ventura for IOS 16.5

g3kk0 commented 12 months ago

I noticed a similar issue when selecting macOs Base System on this screen.

What worked for me was not manually selecting anything and allowing the boot screen to auto select macOs Base System by just waiting (appears to have a 30-60 timeout).

kocoman2 commented 10 months ago

is there any way to get the error log?

metal3d commented 8 months ago

What worked for me was not manually selecting anything and allowing the boot screen to auto select macOs Base System by just waiting (appears to have a 30-60 timeout).

On my side, it didn't changed anything. It restarts again and again, and I only see the scree you show. I never had the screen to use disk utility tool.

I see this after 2 reboots...

Screenshot from 2023-10-22 15-53-03

metal3d commented 8 months ago

This is the exact thing I see:

Screenshot from 2023-10-22 15-57-22 Screenshot from 2023-10-22 15-57-34 Screenshot from 2023-10-22 15-57-40 Screenshot from 2023-10-22 15-57-59 Screenshot from 2023-10-22 15-58-49

And then go back to the first image, again and again...

metal3d commented 8 months ago

OK, the AMD CPUs are not supported.

Kaympe20 commented 8 months ago

This issue also occurs in OSX-KVM

SuperKeith333 commented 7 months ago

Try adding the boot options from sosumi launch from snap. I had the same problem on both my computers and it fixed it