mirror of
https://github.com/sickcodes/Docker-OSX.git
synced 2026-01-13 13:53:28 +01:00
Screen resolution can not change. #205
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 @ccb-github on GitHub (Jun 27, 2021).
It seems that whatever the HEIGHT, WIDTH I set at the "docker run" command, I get the same size of window at startup. However if I check the "zoom to fit" option, it could resize the window, as well as all the "zoom" option in the top menu bar. And when I enter the guest system. It only has one resolution available in system preference>display , so the inner window can display same amount of thing whatever. I think I face the same issue with sosumi, Yet another tool run mac in the kvm,
@sickcodes commented on GitHub (Jun 28, 2021):
https://github.com/sickcodes/Docker-OSX#changing-display-resolution
@ccb-github commented on GitHub (Jun 29, 2021):
Thanks, I did not realize this was on the mainpage, obviously I have not read it carefully. But I have a little question, is the MASTER_PLIST_URL setting needed for the resolution change to work, and could I download the plist file to local instead of using url. I still stuck at network issue right now, lol...
@sickcodes commented on GitHub (Jun 29, 2021):
Yeah so the plist URL creates boot disk at runtime, as opposed to using the existing one, which has 1920x1080
@ccb-github commented on GitHub (Jul 8, 2021):
Hello again, I find myself stuck at request ...443 ... error, curl 16 error in the HTTP2 framing layer kind of network error. And I did managed to download the image you provide and used it in naked image; and I update the system to big-sur successfully. But I was not fully understand the concept of image and container, and everytime I start the container use docker run command. For troubleshooting this problem, I even delete all the file under /var/lib/docker and reinstall docker. But I still facing this kind of network problem, I was wondering if you could give me a hint.