starred/Docker-OSX
1
0
Fork 0
mirror of https://github.com/sickcodes/Docker-OSX.git synced 2026-01-11 21:10:25 +01:00
Code Issues 411 Packages Projects Releases Wiki Activity

Sonoma reboot loop after install with missing "libSystem.8.dylib" #617

New Issue
Open
opened 2025-12-29 01:23:46 +01:00 by adam · 7 comments
adam commented 2025-12-29 01:23:46 +01:00
Owner
Copy Link

Originally created by @kurbar on GitHub (Sep 23, 2024).

Doing this all on an Ubuntu 24.04 server.

Steps

  1. Cloned this repo
  2. Built a base Sonoma image - docker build -t docker-osx:sonoma --build-arg SHORTNAME=sonoma --build-arg SIZE=30G .
  3. Build a VNC image from the created base image - docker build -t docker-osx:sonoma-vnc -f vnc-version/Dockerfile --build-arg SHORTNAME=sonoma --build-arg SIZE=30G --build-arg BASE_IMAGE=docker-osx:sonoma .
  4. started a container from said image - docker run -d -it --name osx-sonoma --device /dev/kvm --device /dev/snd -p 8888:5999 -p 50922:10022 --privileged docker-osx:sonoma-vnc
  5. Opened an SSH tunnel from local computer to proxy VNC port
  6. Successfully accessed Sonoma from VNC
  7. Created new APFS partition of larger QEMU disk
  8. Reinstalled Sonoma via Recovery
  9. Tried to boot from newly created and installed partition

image

Did the same steps with Ventura and that installation worked.

Originally created by @kurbar on GitHub (Sep 23, 2024). Doing this all on an Ubuntu 24.04 server. ## Steps 1. Cloned this repo 2. Built a base Sonoma image - `docker build -t docker-osx:sonoma --build-arg SHORTNAME=sonoma --build-arg SIZE=30G .` 3. Build a VNC image from the created base image - `docker build -t docker-osx:sonoma-vnc -f vnc-version/Dockerfile --build-arg SHORTNAME=sonoma --build-arg SIZE=30G --build-arg BASE_IMAGE=docker-osx:sonoma .` 4. started a container from said image - `docker run -d -it --name osx-sonoma --device /dev/kvm --device /dev/snd -p 8888:5999 -p 50922:10022 --privileged docker-osx:sonoma-vnc` 5. Opened an SSH tunnel from local computer to proxy VNC port 6. Successfully accessed Sonoma from VNC 7. Created new APFS partition of larger QEMU disk 8. Reinstalled Sonoma via Recovery 9. Tried to boot from newly created and installed partition ![image](https://github.com/user-attachments/assets/36290ef0-f301-4274-b818-1e19c7619efa) Did the same steps with Ventura and that installation worked.
adam commented 2025-12-29 01:23:46 +01:00
Author
Owner
Copy Link

@MendesCorporation commented on GitHub (Sep 27, 2024):

same here

@MendesCorporation commented on GitHub (Sep 27, 2024): same here
adam commented 2025-12-29 01:23:46 +01:00
Author
Owner
Copy Link

@HyperfocusArtisan commented on GitHub (Sep 30, 2024):

Having the same problem. Ventura works just fine, but Sonoma keeps rebooting

@HyperfocusArtisan commented on GitHub (Sep 30, 2024): Having the same problem. Ventura works just fine, but Sonoma keeps rebooting
adam commented 2025-12-29 01:23:47 +01:00
Author
Owner
Copy Link

@kurbar commented on GitHub (Oct 2, 2024):

I think I got Sonoma working now by using the following run command:

docker run -d -it --name osx-sonoma --device /dev/kvm --device /dev/snd -p 8888:5999 -p 50922:10022 -e CPU='Haswell-noTSX' -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on' -e RAM=4 --privileged docker-osx:sonoma-vnc

After installing Sonoma via recovery it booted up and seems to work properly.

@kurbar commented on GitHub (Oct 2, 2024): I think I got Sonoma working now by using the following run command: ``` docker run -d -it --name osx-sonoma --device /dev/kvm --device /dev/snd -p 8888:5999 -p 50922:10022 -e CPU='Haswell-noTSX' -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on' -e RAM=4 --privileged docker-osx:sonoma-vnc ``` After installing Sonoma via recovery it booted up and seems to work properly.
adam commented 2025-12-29 01:23:47 +01:00
Author
Owner
Copy Link

@wahaj4311 commented on GitHub (Nov 14, 2024):

I think I got Sonoma working now by using the following run command:

docker run -d -it --name osx-sonoma --device /dev/kvm --device /dev/snd -p 8888:5999 -p 50922:10022 -e CPU='Haswell-noTSX' -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on' -e RAM=4 --privileged docker-osx:sonoma-vnc

After installing Sonoma via recovery it booted up and seems to work properly.

How do you access vnc?
What's the pass i followed exactly as you do but unable to login maybe due to pass.
I tried complete install acc to official ended up with untitled disk and on same screen.

@wahaj4311 commented on GitHub (Nov 14, 2024): > I think I got Sonoma working now by using the following run command: > > ``` > docker run -d -it --name osx-sonoma --device /dev/kvm --device /dev/snd -p 8888:5999 -p 50922:10022 -e CPU='Haswell-noTSX' -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on' -e RAM=4 --privileged docker-osx:sonoma-vnc > ``` > > After installing Sonoma via recovery it booted up and seems to work properly. How do you access vnc? What's the pass i followed exactly as you do but unable to login maybe due to pass. I tried complete install acc to official ended up with untitled disk and on same screen.
adam commented 2025-12-29 01:23:47 +01:00
Author
Owner
Copy Link

@binyamin555 commented on GitHub (Nov 30, 2024):

@wahaj4311

I was able to install both MacOS Ventura & MacOS Sonoma using these commands, and access them using VNC.

Do note that you'll need to change the external ports so that they will not collide (I'm using 5999 and 5998).

Not sure what port 50922 is for :/

MacOS Ventura (13)

docker run -i \
    --device /dev/kvm \
    -p 50922:10022 \
    -p 5999:5999 \
    -v /tmp/.X11-unix:/tmp/.X11-unix \
    -e "DISPLAY=${DISPLAY:-:0.0}" \
    -e "SHORTNAME=ventura" \
    -e EXTRA="-display none -vnc 0.0.0.0:99,password=off" \
    sickcodes/docker-osx:latest

MacOS Sonoma (14)

docker run -it \
    --device /dev/kvm \
    -p 50922:10022 \
    -p 5999:5999 \
    -v /tmp/.X11-unix:/tmp/.X11-unix \
    -e "DISPLAY=${DISPLAY:-:0.0}" \
    -e GENERATE_UNIQUE=true \
    -e CPU='Haswell-noTSX' \
    -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on' \
    -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom-sonoma.plist' \
    -e "SHORTNAME=sonoma" \
    -e EXTRA="-display none -vnc 0.0.0.0:99,password=off" \
    sickcodes/docker-osx:latest
@binyamin555 commented on GitHub (Nov 30, 2024): @wahaj4311 I was able to install both MacOS Ventura & MacOS Sonoma using these commands, and access them using VNC. Do note that you'll need to change the external ports so that they will not collide (I'm using 5999 and 5998). Not sure what port 50922 is for :/ ## MacOS Ventura (13) ```sh docker run -i \ --device /dev/kvm \ -p 50922:10022 \ -p 5999:5999 \ -v /tmp/.X11-unix:/tmp/.X11-unix \ -e "DISPLAY=${DISPLAY:-:0.0}" \ -e "SHORTNAME=ventura" \ -e EXTRA="-display none -vnc 0.0.0.0:99,password=off" \ sickcodes/docker-osx:latest ``` ## MacOS Sonoma (14) ```sh docker run -it \ --device /dev/kvm \ -p 50922:10022 \ -p 5999:5999 \ -v /tmp/.X11-unix:/tmp/.X11-unix \ -e "DISPLAY=${DISPLAY:-:0.0}" \ -e GENERATE_UNIQUE=true \ -e CPU='Haswell-noTSX' \ -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on' \ -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom-sonoma.plist' \ -e "SHORTNAME=sonoma" \ -e EXTRA="-display none -vnc 0.0.0.0:99,password=off" \ sickcodes/docker-osx:latest ```
adam commented 2025-12-29 01:23:48 +01:00
Author
Owner
Copy Link

@nreith commented on GitHub (Dec 13, 2024):

Out of curiosity, why vnc?

@nreith commented on GitHub (Dec 13, 2024): Out of curiosity, why vnc?
adam commented 2025-12-29 01:23:48 +01:00
Author
Owner
Copy Link

@binyamin555 commented on GitHub (Dec 16, 2024):

Out of curiosity, why vnc?

What are the alternatives?

@binyamin555 commented on GitHub (Dec 16, 2024): > Out of curiosity, why vnc? What are the alternatives?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
enhancement
following upstream developments
good first issue
help wanted
invalid
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Docker-OSX#617
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?