starred/Docker-OSX-sickcodes
1
0
Fork 0
mirror of https://github.com/sickcodes/Docker-OSX.git synced 2026-07-22 21:08:39 +02:00
Code Issues 411 Packages Projects Releases Wiki Activity

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

New Issue
Open
opened 2025-12-29 06:19:55 +01:00 by adam · 8 comments
adam commented 2025-12-29 06:19:55 +01:00
Owner
Copy Link
Copy Source

Originally created by @aditya-upadhye on GitHub (Nov 30, 2022).

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].

Originally created by @aditya-upadhye on GitHub (Nov 30, 2022). 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].
adam commented 2025-12-29 06:19:56 +01:00
Author
Owner
Copy Link
Copy Source

@eialanjones commented on GitHub (Dec 6, 2022):

For me, just disconecting the internet solve the problem

@eialanjones commented on GitHub (Dec 6, 2022): For me, just disconecting the internet solve the problem
adam commented 2025-12-29 06:19:56 +01:00
Author
Owner
Copy Link
Copy Source

@nigelterry commented on GitHub (Dec 10, 2022):

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

@nigelterry commented on GitHub (Dec 10, 2022): I have this issue too. I've tried both of these solutions, and neither works for me.
adam commented 2025-12-29 06:19:56 +01:00
Author
Owner
Copy Link
Copy Source

@omeraydindev commented on GitHub (Dec 15, 2022):

For me, just disconecting the internet solve the problem

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

@omeraydindev commented on GitHub (Dec 15, 2022): > For me, just disconecting the internet solve the problem I was having the same issue, this worked like a charm -- thanks @eialanjones
adam commented 2025-12-29 06:19:56 +01:00
Author
Owner
Copy Link
Copy Source

@rotdrop commented on GitHub (Feb 19, 2023):

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 commented on GitHub (Feb 19, 2023): > 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?
adam commented 2025-12-29 06:19:56 +01:00
Author
Owner
Copy Link
Copy Source

@rotdrop commented on GitHub (Feb 19, 2023):

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 commented on GitHub (Feb 19, 2023): > 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 ...
adam commented 2025-12-29 06:19:57 +01:00
Author
Owner
Copy Link
Copy Source

@rotdrop commented on GitHub (Feb 19, 2023):

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
@rotdrop commented on GitHub (Feb 19, 2023): > > 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
adam commented 2025-12-29 06:19:57 +01:00
Author
Owner
Copy Link
Copy Source

@XjSv commented on GitHub (Mar 4, 2023):

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.

@XjSv commented on GitHub (Mar 4, 2023): 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.
adam commented 2025-12-29 06:19:57 +01:00
Author
Owner
Copy Link
Copy Source

@wugh commented on GitHub (Mar 11, 2023):

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.

@wugh commented on GitHub (Mar 11, 2023): > > > 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.
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 labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Docker-OSX-sickcodes#428