[GH-ISSUE #297] Screen resolution can not change. #206

New issue

Closed

opened 2026-02-27 22:08:30 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 22:08:30 +03:00

Owner

Originally created by @ccb-github on GitHub (Jun 27, 2021).
Original GitHub issue: https://github.com/sickcodes/Docker-OSX/issues/297

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,

Originally created by @ccb-github on GitHub (Jun 27, 2021). Original GitHub issue: https://github.com/sickcodes/Docker-OSX/issues/297 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,

kerem closed this issue

2026-02-27 22:08:31 +03:00

kerem commented

2026-02-27 22:08:31 +03:00

Author

Owner

@sickcodes commented on GitHub (Jun 28, 2021):

https://github.com/sickcodes/Docker-OSX#changing-display-resolution

@sickcodes commented on GitHub (Jun 28, 2021): https://github.com/sickcodes/Docker-OSX#changing-display-resolution

kerem commented

2026-02-27 22:08:31 +03:00

Author

Owner

@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...

@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...

kerem commented

2026-02-27 22:08:31 +03:00

Author

Owner

@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

@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

kerem commented

2026-02-27 22:08:31 +03:00

Author

Owner

@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.

@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.

kerem referenced this issue

2026-02-27 23:01:52 +03:00

[PR #206] [MERGED] Use RAM=max or RAM=half to suit all machines, dynamically. #731