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

Running the same container afterwards #12

New Issue
Closed
opened 2025-12-28 23:20:53 +01:00 by adam · 7 comments
adam commented 2025-12-28 23:20:53 +01:00
Owner
Copy Link

Originally created by @igaurab on GitHub (Jun 5, 2020).

Hi, although I do not know how to work with docker, I managed to install it and was able to run and install my Mac os following the README and reading through the issues.

The problem now I am having is how do I get back my MacOs that I had installed. I tried running docker start of the previously created container, but it only prints out the container id, and if I try running the docker run **** command which was prev used it creates a new instance of container. I think this is what was supposed to happen but, I am getting lost here.

How do I re run my prev created container, i guess

Thanks

Originally created by @igaurab on GitHub (Jun 5, 2020). Hi, although I do not know how to work with docker, I managed to install it and was able to run and install my Mac os following the README and reading through the issues. The problem now I am having is how do I get back my MacOs that I had installed. I tried running docker start <container-id> of the previously created container, but it only prints out the container id, and if I try running the `docker run ****` command which was prev used it creates a new instance of container. I think this is what was supposed to happen but, I am getting lost here. **How do I re run my prev created container, i guess** Thanks
adam closed this issue 2025-12-28 23:20:54 +01:00
adam commented 2025-12-28 23:20:54 +01:00
Author
Owner
Copy Link

@sickcodes commented on GitHub (Jun 5, 2020):

Try the docker start command

@sickcodes commented on GitHub (Jun 5, 2020): Try the `docker start` command
adam commented 2025-12-28 23:20:54 +01:00
Author
Owner
Copy Link

@igaurab commented on GitHub (Jun 5, 2020):

Hi I tried docker start container-id and it did nothing? Just prints the container id and nothing

@igaurab commented on GitHub (Jun 5, 2020): Hi I tried `docker start container-id` and it did nothing? Just prints the container id and nothing
adam commented 2025-12-28 23:20:55 +01:00
Author
Owner
Copy Link

@sickcodes commented on GitHub (Jun 5, 2020):

The container is running, which means it might not be the right machine, or it didn't start correct.

Open all of them

docker start $(docker ps -q --all)
docker start $(docker ps -q --all --filter "ancestor=sickcodes/docker-osx")

and then close the ones you don't want

And then docker ps and save that name

then you can do docker start

@sickcodes commented on GitHub (Jun 5, 2020): The container is running, which means it might not be the right machine, or it didn't start correct. Open all of them ``` docker start $(docker ps -q --all) docker start $(docker ps -q --all --filter "ancestor=sickcodes/docker-osx") ``` and then close the ones you don't want And then `docker ps` and save that name then you can do docker start
adam commented 2025-12-28 23:20:56 +01:00
Author
Owner
Copy Link

@sickcodes commented on GitHub (Jun 6, 2020):

Please check the readme for new instructions including how to launch the old machine

@sickcodes commented on GitHub (Jun 6, 2020): Please check the readme for new instructions including how to launch the old machine
adam commented 2025-12-28 23:20:57 +01:00
Author
Owner
Copy Link

@gameliee commented on GitHub (Jun 10, 2020):

I have the same problem as @igaurab. Here's the log

$ docker start 70766a2c9a69
70766a2c9a69

$ docker ps --all --filter "ancestor=sickcodes/docker-osx"
CONTAINER ID        IMAGE                  COMMAND                CREATED             STATUS                      PORTS               NAMES
70766a2c9a69        sickcodes/docker-osx   "./OpenCore-Boot.sh"   3 hours ago         Exited (1) 13 seconds ago                       elastic_varahamihira

I couldn't figure out how to start the installed image. Helps would be appreciate, thanks.

@gameliee commented on GitHub (Jun 10, 2020): I have the same problem as @igaurab. Here's the log ```bash $ docker start 70766a2c9a69 70766a2c9a69 $ docker ps --all --filter "ancestor=sickcodes/docker-osx" CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 70766a2c9a69 sickcodes/docker-osx "./OpenCore-Boot.sh" 3 hours ago Exited (1) 13 seconds ago elastic_varahamihira ``` I couldn't figure out how to start the installed image. Helps would be appreciate, thanks.
adam commented 2025-12-28 23:20:57 +01:00
Author
Owner
Copy Link

@lucasfp13 commented on GitHub (Jun 16, 2020):

I am having the same problem of @ntd94 , if anyone knows how to fix this it would be great, thanks!

@lucasfp13 commented on GitHub (Jun 16, 2020): I am having the same problem of @ntd94 , if anyone knows how to fix this it would be great, thanks!
adam commented 2025-12-28 23:20:57 +01:00
Author
Owner
Copy Link

@RockJohnson503 commented on GitHub (Aug 7, 2020):

sudo chmod 666 /dev/kvm @ntd94 @lucasfjportela @igaurab

@RockJohnson503 commented on GitHub (Aug 7, 2020): sudo chmod 666 /dev/kvm @ntd94 @lucasfjportela @igaurab
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#12
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?