mirror of
https://github.com/sickcodes/Docker-OSX.git
synced 2026-01-13 13:53:28 +01:00
Support with big-sur image portability #180
Reference in New Issue
Block a user
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 @ficofer on GitHub (Apr 28, 2021).
Team, thanks for this amazing project! I am reaching out to ask for help for something I am not able to complete apparently just checking if I am doing something wrong, or is not possible.
I manage to run Big-sur with the following command:
This start Big-sure instalation leaving me with a
(qemu)prompt where I need to change the vnc user password to be able to connect via VNC.I am able to install and boot big-sur, install xcode, brew, fastlane, ruby, enable ssh and log in via ssh and even reboot the machine, but when I try to create an image out of this container or copy the existing img from the dir (I think its merged) of the overlay-fs and start a new container with this image nothing happens its like the docker commands get stuck after hitting enter.
I have try doing a docker commit as well and trying a docker run of the docker image committed but the same results appears.
I would really appreciate if anyone have donde this with big-sur and can guide me / help me in how to make the foreground running container portable via an image file and that I could restart it with my work saved there but with no qemu prompt.
Thanks a lot in advance for the help/guidance.
@sickcodes commented on GitHub (Apr 29, 2021):
Have you tried
docker start -ai abc123xyz567from https://github.com/sickcodes/Docker-OSX#start-the-same-container-later-persistent-disk@ficofer commented on GitHub (Apr 29, 2021):
I try with docker stop/start and with docker commit, both return an empty resposive container. I am trying with the img approach here https://github.com/sickcodes/Docker-OSX#container-creation-examples
And I got the container dying
@ficofer commented on GitHub (Apr 29, 2021):
cant really spot the problem more than
chown: cannot access '': No such file or directorythat I am not sure what it refers to@sickcodes commented on GitHub (May 4, 2021):
I think it's
vendor=GenuineIntelupstream changes, looking into it now@sickcodes commented on GitHub (May 4, 2021):
did you make the container on a different machine? can you show the output of the new issue command?
@sickcodes commented on GitHub (May 4, 2021):
Please add the following lines and you will be able to boot Big Sur!
@ficofer commented on GitHub (May 6, 2021):
@sickcodes thanks for getting back to me! now I am a step back I cant start big-sur image to create my golden/first image... when I try to boot like this:
I have not try the naked cause I did not create first the img with all the things installed yet.
Note: the template for commands when you create a new issue have disappear for some reason ?
@ficofer commented on GitHub (May 6, 2021):
Sorry if I am cutting of something from the log, I am trying to go over all of it and thats what I see strange there.
@sickcodes commented on GitHub (May 9, 2021):
docker pull sickcodes/docker-osx:big-sur@sickcodes commented on GitHub (May 9, 2021):
Please docker pull latest version,
supermin: root UUID is longer than 16 byteswas fixed a few days ago by me.