[Fix]: Ventura stuck when trying to update itself during the installation process

[aditya-upadhye]

When installing Ventura, the Software Update seems to be a part of the installation process and this attempt to Update gets the installation process stuck.

The fix for this bug is to Delete the Container, create a new container for Ventura using the commands given in README and while formatting the largest size of Hard Disk available in the Disk Utility, choose Mac OS Extended (Journaled) as the Format [and not APFS].

[eialanjones]

For me, just disconecting the internet solve the problem

[nigelterry]

I have this issue too. I've tried both of these solutions, and neither works for me.

[omeraydindev]

For me, just disconecting the internet solve the problem

I was having the same issue, this worked like a charm -- thanks @eialanjones

[rotdrop]

For me, just disconecting the internet solve the problem

What do you mean by this? Bringing down the network interface of the host system? Is it possible to just disconnect the docker container?

[rotdrop]

When installing Ventura, the Software Update seems to be a part of the installation process and this attempt to Update gets the installation process stuck.

The fix for this bug is to Delete the Container, create a new container for Ventura using the commands given in README and while formatting the largest size of Hard Disk available in the Disk Utility, choose Mac OS Extended (Journaled) as the Format [and not APFS].

This worked for me, at least once ...

[rotdrop]

For me, just disconecting the internet solve the problem

What do you mean by this? Bringing down the network interface of the host system? Is it possible to just disconnect the docker container?

For the record:

• run docker ps, denote the container id
• run docker network ls, note down the id of the bridge network
• should you hit this error, disconnect the bridge network: docker network disconnect NETORK_ID CONTAINER_ID
• reboot, using the running container, should be available from the "apple menu"
• next time things should go through, without being stuck in the updater
• afterwards it should be ok to reconnect the network

[XjSv]

Thanks @rotdrop, docker network disconnect NETORK_ID CONTAINER_ID worked for me but I had to do it during the second half of the installation. If you do it before the installation starts, it fails with a 'can't contact recovery server' error.

I also formatted the disk using Mac OS Extended (Journaled) format, if that matters.

[wugh]

For me, just disconecting the internet solve the problem

What do you mean by this? Bringing down the network interface of the host system? Is it possible to just disconnect the docker container?

For the record:

• run docker ps, denote the container id
• run docker network ls, note down the id of the bridge network
• should you hit this error, disconnect the bridge network: docker network disconnect NETORK_ID CONTAINER_ID
• reboot, using the running container, should be available from the "apple menu"
• next time things should go through, without being stuck in the updater
• afterwards it should be ok to reconnect the network

when should I disconnect the network during the install process.