starred/Docker-OSX-sickcodes
1
0
Fork 0
mirror of https://github.com/sickcodes/Docker-OSX.git synced 2026-01-14 15:43:32 +01:00
Code Issues 411 Packages Projects Releases Wiki Activity

Xcode can't run simulator due to docker not allowing more than "3.91gb" of RAM #564

New Issue
Closed
opened 2025-12-29 06:21:23 +01:00 by adam · 4 comments
adam commented 2025-12-29 06:21:23 +01:00
Owner
Copy Link

Originally created by @SaintCodak on GitHub (Jan 15, 2024).

Ive tried to run multiple containers of ventura and download xcode. it seems to work, but even if I specify how much RAM I want upon creation, the OS never has more than 4, which is needed for xcode simulation. I found a closed issue relating, but it didn't help and is old. What am I doing wrong?

Im on Linux Mint, pretty fresh install. I know docker is native and should have access to all RAM, but Xcode doesn't see that maybe? Has anyone been successful here?

Originally created by @SaintCodak on GitHub (Jan 15, 2024). Ive tried to run multiple containers of ventura and download xcode. it seems to work, but even if I specify how much RAM I want upon creation, the OS never has more than 4, which is needed for xcode simulation. I found a closed issue relating, but it didn't help and is old. What am I doing wrong? Im on Linux Mint, pretty fresh install. I know docker is native and should have access to all RAM, but Xcode doesn't see that maybe? Has anyone been successful here?
adam closed this issue 2025-12-29 06:21:23 +01:00
adam commented 2025-12-29 06:21:24 +01:00
Author
Owner
Copy Link

@QuentinSc commented on GitHub (Jan 21, 2024):

what was the solution ?

@QuentinSc commented on GitHub (Jan 21, 2024): what was the solution ?
adam commented 2025-12-29 06:21:24 +01:00
Author
Owner
Copy Link

@cesarsicas commented on GitHub (Jun 4, 2024):

Same here, any update?

I already increased the container memory on docker to 12GB but nothing changed. Is it possible to make the SO recognize the new available memory or bypass this problem ?

Captura de tela 2024-06-04 152251

@cesarsicas commented on GitHub (Jun 4, 2024): Same here, any update? I already increased the container memory on docker to 12GB but nothing changed. Is it possible to make the SO recognize the new available memory or bypass this problem ? ![Captura de tela 2024-06-04 152251](https://github.com/sickcodes/Docker-OSX/assets/7783112/27f26368-bf69-42fe-8d42-7930c0ed7d4f)
adam commented 2025-12-29 06:21:24 +01:00
Author
Owner
Copy Link

@skon-L commented on GitHub (Nov 12, 2024):

Same,problem solved?

@skon-L commented on GitHub (Nov 12, 2024): Same,problem solved?
adam commented 2025-12-29 06:21:25 +01:00
Author
Owner
Copy Link

@claudioscheer commented on GitHub (Dec 18, 2024):

@skon-L @QuentinSc https://github.com/sickcodes/Docker-OSX/issues/622#issuecomment-1936503355

@claudioscheer commented on GitHub (Dec 18, 2024): @skon-L @QuentinSc https://github.com/sickcodes/Docker-OSX/issues/622#issuecomment-1936503355
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-sickcodes#564
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?