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

Macos starts from the installation over and over again #96

New Issue
Closed
opened 2025-12-28 23:24:08 +01:00 by adam · 10 comments
adam commented 2025-12-28 23:24:08 +01:00
Owner
Copy Link

Originally created by @itsoulos on GitHub (Dec 28, 2020).

Dear all I have followed your instructions to install macos but
after every successful installation the procedure starts again instead of booting to the installed disk
What is wrong with my installation?

Best regards
Giannis Tsoulos

Originally created by @itsoulos on GitHub (Dec 28, 2020). Dear all I have followed your instructions to install macos but after every successful installation the procedure starts again instead of booting to the installed disk What is wrong with my installation? Best regards Giannis Tsoulos
adam closed this issue 2025-12-28 23:24:08 +01:00
adam commented 2025-12-28 23:24:09 +01:00
Author
Owner
Copy Link

@thematrixdev commented on GitHub (Dec 29, 2020):

Do you see the boot menu (showing two hard drives) after install? Have you chosen the one you have installed OSX to (instead of the base volume)?

@thematrixdev commented on GitHub (Dec 29, 2020): Do you see the boot menu (showing two hard drives) after install? Have you chosen the one you have installed OSX to (instead of the base volume)?
adam commented 2025-12-28 23:24:09 +01:00
Author
Owner
Copy Link

@itsoulos commented on GitHub (Dec 29, 2020):

No I see only the drive to install macos

Here is the command that I execute as root

docker run --privileged -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix sickcodes/docker-osx

@itsoulos commented on GitHub (Dec 29, 2020): No I see only the drive to install macos Here is the command that I execute as root docker run --privileged -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix sickcodes/docker-osx
adam commented 2025-12-28 23:24:10 +01:00
Author
Owner
Copy Link

@thematrixdev commented on GitHub (Dec 29, 2020):

The new drive will only show up after installation. Before installation, did you use "disk utility" to "erase" and "create" on the LARGEST drive?

@thematrixdev commented on GitHub (Dec 29, 2020): The new drive will only show up after installation. Before installation, did you use "disk utility" to "erase" and "create" on the LARGEST drive?
adam commented 2025-12-28 23:24:10 +01:00
Author
Owner
Copy Link

@itsoulos commented on GitHub (Dec 29, 2020):

Yes I have seen the new drive but it has been lost when I closed the application docker and restart it

@itsoulos commented on GitHub (Dec 29, 2020): Yes I have seen the new drive but it has been lost when I closed the application docker and restart it
adam commented 2025-12-28 23:24:11 +01:00
Author
Owner
Copy Link

@thematrixdev commented on GitHub (Dec 29, 2020):

Oh I see. The docker volume does not presist so you have lost the installation. I would suggest you using docker-compose. git clone this project, and docker-compose up -d.

@thematrixdev commented on GitHub (Dec 29, 2020): Oh I see. The docker volume does not presist so you have lost the installation. I would suggest you using docker-compose. `git clone` this project, and `docker-compose up -d`.
adam commented 2025-12-28 23:24:12 +01:00
Author
Owner
Copy Link

@itsoulos commented on GitHub (Dec 29, 2020):

So, you say to execute docker-compose up -d after the installation?

@itsoulos commented on GitHub (Dec 29, 2020): So, you say to execute docker-compose up -d after the installation?
adam commented 2025-12-28 23:24:12 +01:00
Author
Owner
Copy Link

@thematrixdev commented on GitHub (Dec 29, 2020):

No. Use docker-compose up -d from the very begining, so the "docker volume" will be managed and persist by docker-compose. After installation, use and shut-down, you can use docker-compose up -d next time you need to use OSX.

@thematrixdev commented on GitHub (Dec 29, 2020): No. Use `docker-compose up -d` from the very begining, so the "docker volume" will be managed and persist by `docker-compose`. After installation, use and shut-down, you can use `docker-compose up -d` next time you need to use OSX.
adam commented 2025-12-28 23:24:12 +01:00
Author
Owner
Copy Link

@sickcodes commented on GitHub (Dec 29, 2020):

docker ps to get the container ID

docker start containerid

Otherwise you'll get a new box every time.

@sickcodes commented on GitHub (Dec 29, 2020): `docker ps` to get the container ID `docker start containerid` Otherwise you'll get a new box every time.
adam commented 2025-12-28 23:24:12 +01:00
Author
Owner
Copy Link

@itsoulos commented on GitHub (Dec 29, 2020):

I have managed to install it but the MACOS can not see IOS Devices

@itsoulos commented on GitHub (Dec 29, 2020): I have managed to install it but the MACOS can not see IOS Devices
adam commented 2025-12-28 23:24:13 +01:00
Author
Owner
Copy Link

@sickcodes commented on GitHub (Jan 4, 2021):

I will have a prebuilt image ready soon

@sickcodes commented on GitHub (Jan 4, 2021): I will have a prebuilt image ready soon
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#96
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?