mirror of
https://github.com/sickcodes/Docker-OSX.git
synced 2026-04-27 16:45:49 +03:00
[GH-ISSUE #906] Suddenly not able to work #674
Labels
No labels
bug
documentation
enhancement
following upstream developments
good first issue
help wanted
invalid
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Docker-OSX#674
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @Quin452 on GitHub (Nov 9, 2025).
Original GitHub issue: https://github.com/sickcodes/Docker-OSX/issues/906
I managed to get a container running, even creating my own images and tweaking the RAM, etc.
However, when I come to running it today, I get a whole mix of different errors. Some "panic mode", some AppleVID is not yet installed as gSystem.
I've tried all previous containers and images, and nothing seems to work anymore.
Even the Sequoia command from this repo ends in a AppleVID is not yet installed, and this is a fresh command and container.
I haven't a clue as to what has caused this sudden break.
@Quin452 commented on GitHub (Nov 9, 2025):
Update: I've been able to get passed those errors.
It's a shame that in that process I deleted all containers and images.
But I think it comes down to something with Podman (I have Podman Desktop installed) or the file ownership/permissions (which I think is the most likely issue).
I want to get this new container running consistently first, and then work on the bugs.
Update 2
As you can see, I've spent an entire day on this. I don't know how, but I was able to get a container running again.
Then I rebooted the Host, and I still get the AppleVID gSystem, and Memory Panic errors when booting anything from the GRUB.
Not entirely too sure what's going on, as I tried to follow my previous debug steps.
Update 3
I've tried shutting down my host machine and turning it back on. The container works again. Rebooting seems to break it.
I will do more tests later. I am tired.
This is strange behaviour.