mirror of
https://github.com/sickcodes/Docker-OSX.git
synced 2026-01-13 13:53:28 +01:00
Can't install Xcode requires newer version of MacOS #23
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 @peterandrewd on GitHub (Jun 8, 2020).
As the title says. Would some be kind enough to let me know how I can install Xcode to sideload apps?
@sickcodes commented on GitHub (Jun 8, 2020):
Really? Let me check now and change to installed a newer build.
I will upload how I sideloaded my unc0ver shorty. It involved signing the release https://dantheman827.github.io/ios-app-signer/
And then installed using OTA plist method. I am not sure if you need a iOS Developer certificate to do OTA app installs by your phone's UUID, but it might.
@peterandrewd commented on GitHub (Jun 8, 2020):
Ok thanks. That would be much appreciated.
Latest Xcode only supports newest Mac OS, and lower Xcode versions don't support iOS 13.5.
I have a developer account so I don't mind doing OTA install method.
Please let me know when you've changed it to a newer build.
@peterandrewd commented on GitHub (Jun 8, 2020):
how's the progress?
@sickcodes commented on GitHub (Jun 8, 2020):
Yeah done, just testing out a new thing I did for the QEMU arguments so any argument can be modified with docker env args:
-e RAM
-e CORES
-e NFS_DISK
-e ROOT_PASS
Etc.
@peterandrewd commented on GitHub (Jun 8, 2020):
Awesome. Love your work.
So to reinstall MacOS with the new image, follow the same steps as before?
@hypermoist commented on GitHub (Jun 8, 2020):
Would love this rn xD
@sickcodes commented on GitHub (Jun 8, 2020):
I will include instructions (in the form of an automated shell script) how to migrate the img to the new container.
But regarding the new version, I would suggest doing the new actual box when I push it
@sickcodes commented on GitHub (Jun 8, 2020):
New version will have the absolute works.
@sickcodes commented on GitHub (Jun 8, 2020):
Hopefully tonight, just stocked up on Red Bull 😂
@peterandrewd commented on GitHub (Jun 8, 2020):
You the man!
Also include instructions for creating a new box for the new OS please
@hypermoist commented on GitHub (Jun 8, 2020):
Damn you, i just ran out XD
@peterandrewd commented on GitHub (Jun 8, 2020):
So eagerly awaiting for the new instructions to run and sideload apps haha
@sickcodes commented on GitHub (Jun 9, 2020):
I’m pretty tired, got a few more things to check.
QEMU crashed unexpectedly, not sure why.
Here’s what I used to do the OTA update if you can’t wait: https://gist.github.com/hramos/774468
You need a domain with SSL, if you don’t want to buy anything just use a .tk domain + Lets Encrypt
Is the app signed yet?
@peterandrewd commented on GitHub (Jun 9, 2020):
Sorry for my lack of knowledge here but how do I use this script? What do I do exactly?
I've just signed up for a domain and gotten an SSL certificate which i'll install in Ubuntu, but confused as to what I do with the manifest.plist script.
@sickcodes commented on GitHub (Jun 9, 2020):
Here is an explanation, https://medium.com/@adrianstanecki/distributing-and-installing-non-market-ipa-application-over-the-air-ota-2e65f5ea4a46
Gotta finish some client work today unfortunately I won't be able to release v2 yet.
Will let everyone know ASAP, will post here and on my twitter http://twitter.com/sickcodes
@peterandrewd commented on GitHub (Jun 9, 2020):
I’ve followed it to a tee. I can access my local server through my iPhone safari browser, I click the install link to the ipa I want to install and it just keeps asking me to open itunes. I have a developer account. Wtf am I doing wrong? I’m pretty frustrated
@peterandrewd commented on GitHub (Jun 9, 2020):
Well I changed something and now the link does sweet fuck all.
Where am I supposed to put the ipa files so it can be added and accessed on my local host server?
@sickcodes commented on GitHub (Jun 10, 2020):
Same directory.
It does require a valid SSL cert
So it cannot be http://localhost
It must be https:// and I am not sure because it alsoneeds a valid SSL certificate. I had been meaning to test IPA downloads with invalid or self signed certs, perhaps installing the certificate first, which should work but that’s why I mentioned .tk and let’s encrypt
Also the URL looks like this
itms-services://?action=download-manifest&url=https://website.com/manifest.plist@peterandrewd commented on GitHub (Jun 10, 2020):
Dont mean to rush you but I really need Catalina to run in QEMU, that other solution has not at all worked out for me.
@peterandrewd commented on GitHub (Jun 11, 2020):
why on earth did you use an old version of Mac OS to begin with?
@machineonamission commented on GitHub (Jun 12, 2020):
Would upgrading within the VM to Catalina work?
edit: ill download and try it myself why not lol
@machineonamission commented on GitHub (Jun 12, 2020):
It didnt work with the default storage amount BUT you can build the dockerfile with any version that gibMacOS supported
then replace
sickcodes/docker-osxwithdocker-osx:latestin your run commandI currently haven't gotten to the desktop or installed xcode yet, but it did boot and it shows macOS Catalina on the install screen.
Edit: I installed Xcode and ran it
@sickcodes commented on GitHub (Jun 12, 2020):
10.15.5 builds fine too.
Old version for stability, same reason LTS kernels exist.
@peterandrewd commented on GitHub (Jun 13, 2020):
I get this error when inputting the above commands. I have downloaded Catalina from gibMacOS.
Usage: docker build [OPTIONS] PATH | URL | -
Build an image from a Dockerfile
How to fix?
@machineonamission commented on GitHub (Jun 13, 2020):
Download the github repository, cd to it, and add a dot to the end iirc
@peterandrewd commented on GitHub (Jun 13, 2020):
Now it does sweet fuck all. Doesn't load anything
I just get: Unable to find image 'docker-osx:latest' locally
@machineonamission commented on GitHub (Jun 13, 2020):
Guess I remembered wrong. I’m pretty sure you need the repo downloaded to
build it though. Google the errors I guess idk
@peterandrewd commented on GitHub (Jun 13, 2020):
Really? That's your solution in trying to help? GTFO off here then.
@AubreyHewes commented on GitHub (Jun 13, 2020):
@peterandrewd Unable to find image 'docker-osx:latest' literally... means you have no image downloaded at that tag name.. so check that it is available locally been built?
docker images..Your previous usage errors on
docker buildactually literally means you are probably not correctly copying the command proposed... i.e. missing a slash or such like..Docker usage is not part of this repo.. linux/macos shell usage is not part of this repo..
An error from a cli command telling you how to use the command is not an error. It is a user error.
@machineonamission commented on GitHub (Jun 13, 2020):
dude, I’m not the owner of the repo. I’m just posting what worked for me.
No need to be so rude
@peterandrewd commented on GitHub (Jun 13, 2020):
well could someone be kind enough to give me a step by step guide?
it does exist: docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
sickcodes/docker-osx latest 86d96fb48732 4 days ago 11.8GB
@AubreyHewes commented on GitHub (Jun 13, 2020):
@peterandrewd A step by step guide on how to use docker? Or read directions?
The image you are displaying is
sickcodes/docker-osx:latestnotdocker-osx:latest(cf your error)... so I assume you have missed a step?Maybe just rename it and get on going?
Possibly be kind enough to apologise to @HexCodeFFF as was only trying to help and there was no need for your type of reaction?
@AubreyHewes commented on GitHub (Jun 13, 2020):
@peterandrewd Possibly be kind enough to apologise to @HexCodeFFF as was only trying to help and there was no need for your type of reaction?
@peterandrewd commented on GitHub (Jun 13, 2020):
Ok I apologise for how I spoke. I am just frustrated.
When I run docker run --privileged -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix sickcodes/docker-osx:latest in theory whatever it's named, it should let me install Catalina. But it still says Mojave on the install screen.
@machineonamission commented on GitHub (Jun 13, 2020):
You have to run the build command successfully first, that’s where it
actually “changes” to Catalina.
@AubreyHewes commented on GitHub (Jun 13, 2020):
@peterandrewd see docs on setting the version...
It is no excuse to talk as you did. Mention and apologize to @HexCodeFFF explicitly and not an off hand oh sorry.
The platform/software you are using is delivered by people. That you are frustrated ok. Keep that to yourself. Ask questions on how to alleviate your problem and be polite there within you can be frustrated.
The way you react. Determines how people see you.. You have a very shallow github profile (means nothing I know).. but such info added with your reactions also tells others what kind of person you are.
@peterandrewd commented on GitHub (Jun 13, 2020):
Ok so ive renamed sickcodes/docker-osx:latest to docker-osx:latest as I was meant to do. But when I copy and paste his above commands: sudo docker build -t docker-osx:latest
--build-arg VERSION=10.15.4
--build-arg SIZE=200G
I get the same error: "docker build" requires exactly 1 argument.
@peterandrewd commented on GitHub (Jun 13, 2020):
Noted. Ive apologised that's all I can do and won't do it again.
@AubreyHewes commented on GitHub (Jun 13, 2020):
@peterandrewd You should apologize direct to the person you have been rude to. i.e. mention and apologize directly (which you have not done). A sign of respect and humility brings you a long way.
I have no time to tell you how to copy-paste commands in your shell.
@peterandrewd commented on GitHub (Jun 13, 2020):
I’m sorry for talking to you the way I did HexCode
@peterandrewd commented on GitHub (Jun 13, 2020):
Now can I please get some help with the codes
@AubreyHewes commented on GitHub (Jun 13, 2020):
@peterandrewd You may be new to GitHub. To mention a person you first use a @.. this way you know that that person may receive your message. Within an issue you are autofilled with names who are in the issue.. why am i explaining this? .. then you can continue. I understand that you did apologise.. though as the person was not mentioned.. they may not ever know. They may be the only person that can help. Do you understand what I am saying?
@peterandrewd commented on GitHub (Jun 13, 2020):
@HexCodeFFF I am sorry for how I spoke to you. Please accept my apology it will not happen again.
@peterandrewd commented on GitHub (Jun 13, 2020):
Yep understood. Still learning. Done.
But now can I please get some help regarding my codes and issue im having.
@AubreyHewes commented on GitHub (Jun 13, 2020):
@peterandrewd what problem do you have? still the invalid docker command usage? did you put the complete command on one line and then use it?
@AubreyHewes commented on GitHub (Jun 13, 2020):
@peterandrewd there are no "codes".. it is mostly knowledge.. asking to fix the "codes" is actually also very depressing.. you should probably ask the "codes" questions on stack or such like...
@peterandrewd commented on GitHub (Jun 13, 2020):
just tried it on 1 line: sudo docker build -t docker-osx:latest --build-arg VERSION=10.15.5 --build-arg SIZE=200G
getting this error: unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/peter/docker-osx:latest/Dockerfile: no such file or directory
@AubreyHewes commented on GitHub (Jun 13, 2020):
@peterandrewd Also it is generally regarded when someone gives a usable answer that the recipient says something.. also a new thing for you.. but as you are learning.. and know everything better I do not really care.
@peterandrewd commented on GitHub (Jun 13, 2020):
wtf? since when did I say I knew everything better?
I have done my due diligence and apologised directly.
@AubreyHewes commented on GitHub (Jun 13, 2020):
@peterandrewd The error is a user error has nothing to do with this repo or any other repo. You should probably fix it or go to the Docker repo and ask there?
@peterandrewd commented on GitHub (Jun 13, 2020):
alrightyyyy thennn
@AubreyHewes commented on GitHub (Jun 13, 2020):
@peterandrewd It is just the attitude... no remorse.. fine. But that makes you who you are
@peterandrewd commented on GitHub (Jun 13, 2020):
I do have remorse. I apologised and meant it. That to me is called remorse.
@AubreyHewes commented on GitHub (Jun 13, 2020):
And I do not have a problem sharing knowledge.. You are welcome
@peterandrewd commented on GitHub (Jun 13, 2020):
You know without me posting about the bug in the 1st place none of this would've even been known. So I think for that AND the fact that I did apologise several times, I deserve some help regarding what to do to boot into Catalina installer.
@sickcodes commented on GitHub (Jun 13, 2020):
You’re still missing the dot at the end
docker build -t mylabel .
The dot means the directory that you are in, it is the missing argument.
docker build -t docker-osx:latest --build-arg VERSION=10.15.4 --build-arg SIZE=200G .docker build -t docker-osx:latest --build-arg VERSION=10.15.4 --build-arg SIZE=200G ./docker build -t docker-osx:latest --build-arg VERSION=10.15.4 --build-arg SIZE=200G $PWDdocker build -t docker-osx:latest --build-arg VERSION=10.15.4 --build-arg SIZE=200G $(pwd)These are all the same
@peterandrewd commented on GitHub (Jun 14, 2020):
@sickcodes Error response from daemon: the Dockerfile (Dockerfile) cannot be empty
what is actually meant to be in the Dockerfile though?
@peterandrewd commented on GitHub (Jun 14, 2020):
It’s the content in the dockerfile I don’t understand.
@ImranR98 commented on GitHub (Jun 14, 2020):
The Dockerfile should have some stuff in it from this repo. I was able to get xcode running with a few simple steps.
git clone https://github.com/sickcodes/Docker-OSX.gitcd Docker-OSXsudo apt install qemu qemu-kvm libvirt-clients libvirt-daemon-system bridge-utils virt-manager- this is the command using APT, check the README for others.docker build -t docker-osx:latest --build-arg VERSION=10.15.5 --build-arg SIZE=64G .sudo chmod 666 /dev/kvm- I had to do this, maybe you won't need to.docker run --privileged -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix docker-osxAll this can be found in the README, I don't get why you were showing attitude and acting like you "deserved" support for a free project someone is maintaining in their free time.
@peterandrewd commented on GitHub (Jun 14, 2020):
I was simply very frustrated. I get my attitude wasn't right, and Ive done my due diligence for that.
I followed your steps and got this error: make: msgfmt: No such file or directory
make: *** [Makefile:150: po/pt.mo] Error 127
==> ERROR: A failure occurred in package().
Aborting..
The command '/bin/sh -c makepkg -si --noconfirm' returned a non-zero code: 4
docker run --privileged -e "DISPLAY=${DISPLAY:-:0.0}" -v /tmp/.X11-unix:/tmp/.X11-unix docker-osx
Unable to find image 'docker-osx:latest' locally
docker: Error response from daemon: pull access denied for docker-osx, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
@ImranR98 commented on GitHub (Jun 14, 2020):
Hmm. Yeah I have no idea what that error means. Although I just realized after my last comment that he's uploaded a docker-compose file, which means that you shouldn't even need to clone and build the repo. Just download the docker-compose file, change the VERSION and SIZE params to your liking, then run
docker-compose up. I was just able to get a working VM in a few minutes with that, maybe worth a shot.@peterandrewd commented on GitHub (Jun 14, 2020):
Thank you. And to actually boot into the new build?
and running that command and doing those steps of course I get an error:
failed to build: The command '/bin/sh -c makepkg -si --noconfirm' returned a non-zero code: 4
@ImranR98 commented on GitHub (Jun 14, 2020):
Not sure what you mean my 'to boot into the new build'. Were you able to run the docker-compose command? If it helps, maybe try starting fresh with a clean slate by deleting all your current containers and images you might have accumulated while troubleshooting.
@peterandrewd commented on GitHub (Jun 14, 2020):
Yeah the docker compose command worked. Did its thing and then at the end gave me that error.
@peterandrewd commented on GitHub (Jun 14, 2020):
Removed and pruned all docker images and still same error. See now I have a reason to be frustrated.
@ImranR98 commented on GitHub (Jun 14, 2020):
Hmm yeah I guess I'd be pretty frustrated too at this point. I can't help but wonder if there's something obvious you missed. How about taking screenshots of your whole process one command after the other up to the point you get stuck? Maybe sickcodes or someone else who knows their stuff can help further.
Also, forget the docker compose idea, doesn't seem to work after all (for me) but the clone and build method should.
@peterandrewd commented on GitHub (Jun 14, 2020):
All screenshots at below link:
https://ufile.io/f/76ba1
And then the next step is the error:
https://ufile.io/5g9e437p
@peterandrewd commented on GitHub (Jun 14, 2020):
Anyone? My frustration level is a 9/10 right now. ANY immediate help would be appreciated
@qcasey commented on GitHub (Jun 14, 2020):
I also ran into that make error for the record.
I think something in the Dockerfile needs to be tweaked but I'm not well versed enough here to do that.
@peterandrewd it might be a while until custom builds are working. If this is critical for some strange reason you may want to look at the original MacOS KVM repo this docker image is based on.
https://github.com/foxlet/macOS-Simple-KVM
@peterandrewd commented on GitHub (Jun 14, 2020):
I can get it to boot into Mojave installer using the docker-compose up command. But it’s still only Mojave.
The other command also still gives me the error
@qcasey commented on GitHub (Jun 14, 2020):
Just saw #39, I'm on mobile but I will try a build without yay later today and post what comes out of that. It may help your original build issue.
I haven't tried docker-compose, can't speak to that
@peterandrewd commented on GitHub (Jun 14, 2020):
thank you id really appreciate that
@qcasey commented on GitHub (Jun 14, 2020):
I removed yay and it built Catalina successfully. @peterandrewd try these great instructions above, but change the git clone to my fork for now. Also do a docker image prune if you haven't already.
docker image prunegit clone https://github.com/qcasey/Docker-OSX.git...cd and the other instructions above@peterandrewd commented on GitHub (Jun 14, 2020):
That worked! thank you so much. You are awesome
@peterandrewd commented on GitHub (Jun 14, 2020):
@qcasey so I'm booted into Catalina. But it won't recognise my iPhone connected via USB. I need that to be able to sideload using Xcode.
Host OS (Linux) see's it, but not macOS on QEMU
@qcasey commented on GitHub (Jun 14, 2020):
#36 mentions this, the solution is being worked on AFAIK
@machineonamission commented on GitHub (Jun 14, 2020):
Haven’t tested it yet, but you can add USB devices by editing open core
boot or whatever it’s called (see #38 )
@peterandrewd commented on GitHub (Jun 14, 2020):
I found opencore.ssh but what parameters or text do I add?
@sickcodes commented on GitHub (Jun 14, 2020):
Updated to Catalina for the original opened issued
SSH added
Ability to add USB via QEMU arg -e EXTRAS and -v of the volume folder