Docker Image disappeared #799
Comments
Same problem for me i think the repo as been shutdown |
|
Facing the exact same issue. |
|
Likewise! |
|
+1 |
1 similar comment
|
+1 |
|
To show you're having the same issue, please click 👍 on the original post instead of making new comments. It notifies/emails everyone who's subscribed to this issue every time a new comment is made. Thanks! |
|
+1 |
|
It's gone from my account. No email or information received as of yet. I've sent an email to Docker Hub support, will update once I hear back... very strange! |
|
Wondering is there any plan to change to other registry service is Docker Hub is not working? |
|
mark |
|
Apple reported the Docker-OSX repository to Docker Hub saying that it violated Apple copyright and Docker Hub moderated the repository. Will update later today when I have more information from Docker Hub. |
|
The DMCA notice:
|
Can you provide a link to the network disk of the tar file, I only recently learned about this project, and I want to experience it |
|
I would also backup the this repo by forking it, Apple is not friendly towards open source projects. I would expect to see a dmca from github any day. |
|
Find those images get banned the exact day I learned this project. I think upload those files onto a cloud disk may temporately resolve the issue? This seems to be an promising project and I actually want to try iy out. |
Forking this repo will likely not help. When youtube-dl was DMCA'd, all forks were also taken down. Cloning would be the best way to back up a repo.
I'll make one reply before moving on, as it's off-topic and risks sparking a lengthy debate. However, I'd like to respectfully challenge the idea that Apple is unfriendly to open-source. Apple released Swift under the permissive Apache 2.0 license, which I doubt they'd do if they weren't friendly towards open-source. That being said, it's well-documented that Apple typically frowns upon hackintosh projects once they become aware of them. I wonder if the inclusion of the OSK key in this project might have been a contributing factor. Regardless of the reason, I'm sure sickcodes will provide an update when possible. |
^^ Corrected |
Cloning into 'OpenCorePkg'... |
Maybe you are using a proxy. Type |
|
For everyone, I have a mirror of the project on my private git. If this get DMCA'd you can download the source from there: https://git.polyfish0.de/mika/Docker-OSX |
it's useless. i can clone this repositories(OpenCorePkg). But when I execute this string of commands, I repeat this error. So I think it's a problem with this mirror |
|
Could we get for Sonoma as well |
PS C:\Docker-OSX> docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" sickcodes/docker-osx:latest |
|
@DevsGrupoCoagro dude, just read this thread. the image has been deleted due to DMCA |
The solution is to read this thread instead of asking randomly. |
|
The best plan of action for anyone wishing to make a docker container is to clone the repo and build your own image locally. Alternately, there is another repo that has similar functionality. |
|
Could be DMCA possible because of this? |
@KTMGv5 Do you have a Sonoma version of the image？Looking forward to your reply, thank you！ |
@JulyIghor I believe the Dmca is about the fact that the docker image was redistributing the macos installer images etc. The reason that this repo hasn't been taken down is because the installer images are downloaded at buildtime (as far as i know), therefore making the repo void of copyright material. If you can figure out a way to inject your own installer iso, the project should work as normal, just less automatically. @sickcodes, considering the ruthlessness of apple's legal team, may I suggest (for now) removing or obfuscating the links you're using to retrieve the OSX installers? Putting them in some sort of secret format should be enough to dissuade github or apple from trying to take down the project. Just a thought. If you think it's fine, then I'm not nearly qualified to say otherwise. |
no |
|
vc tem que seguir instalação dos pacotes do linux e so no momento de instalar iso vc vai fazer usando codigo que disponibilizei, mais antes precisa seguir passos do instalação padrao `` # ARCH UBUNTU DEBIANsudo apt install qemu qemu-kvm libvirt-clients libvirt-daemon-system bridge-utils virt-manager libguestfs-tools CENTOS RHEL FEDORAsudo yum install libvirt qemu-kvm sudo systemctl enable --now libvirtd echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs sudo modprobe kvm |
|
Thank you @criandoideiasoficial, that indeed helped. Then what to do with this message? What am I missing now?
|
|
Got it to work using ventura. Didn't work with Catalina. Didn't try with sonoma Host: Windows 11, WSL 2, Main distro Ubuntu-20, Docker Desktop Steps takenIn Powershell:
I did it again to verify all the steps work in this order on my setup. Hope this helps |
|
Thanks @alejoluc , this also works on Sonoma. |
|
why I always stuck at step macOs Ventura select the disk where you want to install MacOS |
|
To start the system, on AMD processors, you will probably need to add these arguments : My config : W11, WSL2, Ubuntu 20.04, Docker Desktop, Ryzen 5800X |
I should add these arguments on this command |
|
how to install macos sequoia with this |
|
need to install x11-xserver-utils
|
hello，Do you have the image file of the tar package now? If so, can you send me a copy? Thank you |
|
need help idk what is this just need macos ventura working in docker |
also having this issue |
How did you do? I also got the msg: "error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: CANCEL (err 8) |
|
If you get the
Thats it |
|
|
|
docker run -it does anyone know how to solve this one |
|
I think they might've taken it down again |
|
Rather than relying on pirate images hosted on public registries I think the right way is to let the user set an environment variable to fetch their desired version, convert and install it per OSX-KVM. |
|
By following the exact steps provided by @alejoluc, I'm able to enter the installation screen, but then stuck here: I'm looking for fixes to solve this but the solution definitely works, but logs when excuting |
|
anyone found the solution for this disk lock issue ` By following the exact steps provided by @alejoluc, I'm able to enter the installation screen, but then stuck here: I'm looking for fixes to solve this but the solution definitely works, but logs when excuting Originally posted by @shunia in #799 (comment) |
|
This might help you, @rishicodelux and @shunia: In addition to @alejoluc's steps, I followed these additional installation steps (erase a disk), and I was then able to select the disk to install to. |
Delete the ~240gb hard drive with disk utility as described above
It took me a while to troubleshoot this, but following the advice on the thread was able to get bluebubbles/AirMessage up and working on VM of Ventura. Follow alejoluc's instructions INCLUDING using a Ubuntu-20.04 build on WSL. The default install of WSL is a higher version and doesn't let you install QEMU properly and didn't work for me. It looks like this command should install Ventura instead of defaulting to Sonoma. I had to change the port because I was having issues with the one he had set, don't think it makes a difference. I followed the advice of kftof since I have an AMD processor and added in these arguments. Not sure if it's necessary. I might just be dumb, but after the install and everything I was expecting to boot straight into the OS rather than the boot menu so I didn't actually think it worked at first. I had a screen that looked like this-- It took me a while to realize I could just select the Ventura2 HDD to boot up. Stupid me! 😅 I've been able to restart/shutdown and boot up again without needing to do anything more, so I'm happy. I thought I would have to do a little more customization to get the serial keys generated for iCloud authentication but it seems like that was taken care of automatically. Hope this helps others, good luck! |
|
Thanks bro now it works for me, but I have one question, is it possible to increase the RAM of Ventura? it uses 8gb from my host machine but on the Mac settings it shows as 4gbs, so I'm not able to use the virtual device emulator from Android Studio on it. |
|
The error reported above was generated when I compiled on wsl, but it compiled perfectly fine when I used github codespaces.🤯 If anyone is also having problems compiling the image, maybe you could try my method below. Create a new github codespaceGo to Codespaces and create a new github codespace Init and update submoduleYou need to init and update the submodule using the following command git submodule init
git submodule updateUpdate apt and install Docker
sudo apt-get update
sudo apt-get install \
apt-transport-https \
ca-certificates \
curl \
software-properties-common
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
sudo add-apt-repository \
"deb [arch=amd64] https://download.docker.com/linux/ubuntu \
$(lsb_release -cs) \
stable"
sudo apt-get update
sudo apt-get install docker-ce
sudo docker --versionBuild imagedocker build -t sickcodes/docker-osx:latest --build-arg SHORTNAME=sonoma .Save the imagedocker save -o docker-osx.tar sickcodes/docker-osx:latestThen you can download the image to your own machine If you want to load the image, just type the command below docker load -i /path/to/destination/docker-osx.tar |
|
my two cents....maybe an update to the README will be helpful... |
just edit dockefile,add ： ENV http_proxy=http://host:port set proxy |
|
I will have the new DMCA compliant images uploaded shortly (merged #826), I am just asking Docker if they can unlock the old URL (sickcodes/docker-osx:latest) so that all previous tutorials, videos, articles, etc. have the correct URL. |
and others
docker build -t docker-osx --build-arg SHORTNAME=sonoma .
Unable to find image 'sickcodes/docker-osx:sonoma' locally
docker: Error response from daemon: pull access denied for sickcodes/docker-osx, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.
If we go on the on the Docker Hub page there is nothing more.
The text was updated successfully, but these errors were encountered: