Docker Image disappeared #610

Closed
opened 2025-12-29 01:23:10 +01:00 by adam · 69 comments
Owner

Originally created by @techNomad24 on GitHub (Aug 27, 2024).

Originally assigned to: @sickcodes on GitHub.

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.
Screenshot 2024-08-27 122230

Originally created by @techNomad24 on GitHub (Aug 27, 2024). Originally assigned to: @sickcodes on GitHub. # 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. ![Screenshot 2024-08-27 122230](https://github.com/user-attachments/assets/4e30ef7e-6c28-447f-b0b4-a8d059a8622c)
adam added the bug label 2025-12-29 01:23:10 +01:00
adam closed this issue 2025-12-29 01:23:10 +01:00
Author
Owner

@mettek88 commented on GitHub (Aug 27, 2024):

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. Screenshot 2024-08-27 122230

Same problem for me i think the repo as been shutdown

@mettek88 commented on GitHub (Aug 27, 2024): > # 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. ![Screenshot 2024-08-27 122230](https://private-user-images.githubusercontent.com/179397158/361761901-4e30ef7e-6c28-447f-b0b4-a8d059a8622c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ3NjI4MjEsIm5iZiI6MTcyNDc2MjUyMSwicGF0aCI6Ii8xNzkzOTcxNTgvMzYxNzYxOTAxLTRlMzBlZjdlLTZjMjgtNDQ3Zi1iMGI0LWE4ZDA1OWE4NjIyYy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODI3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgyN1QxMjQyMDFaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03ZjJmNTFlMzJkMzM5NmFmZWYxZjk2ZGZjNTU1OWJlMDJhOWViYjM2MWJkMDFhY2I5MWMzODRhMjRlMTA5MjE5JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.Cd2zPAC77oVndR9wDtjTovvgY2kfta4wnrJj3skBh9M) Same problem for me i think the repo as been shutdown
Author
Owner

@ngjiaxue commented on GitHub (Aug 27, 2024):

Facing the exact same issue.
image

@ngjiaxue commented on GitHub (Aug 27, 2024): Facing the exact same issue. ![image](https://github.com/user-attachments/assets/821a32d0-3862-47ad-bc30-a47978eba803)
Author
Owner

@TrevorDrayton03 commented on GitHub (Aug 27, 2024):

Likewise!

@TrevorDrayton03 commented on GitHub (Aug 27, 2024): Likewise!
Author
Owner

@ZimaBlueee commented on GitHub (Aug 28, 2024):

+1

@ZimaBlueee commented on GitHub (Aug 28, 2024): +1
Author
Owner

@Monsteel commented on GitHub (Aug 28, 2024):

+1

@Monsteel commented on GitHub (Aug 28, 2024): +1
Author
Owner

@Avi0n commented on GitHub (Aug 28, 2024):

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!

@Avi0n commented on GitHub (Aug 28, 2024): To show you're having the same issue, please click :+1: 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!
Author
Owner

@miniwater commented on GitHub (Aug 28, 2024):

+1

@miniwater commented on GitHub (Aug 28, 2024): +1
Author
Owner

@sickcodes commented on GitHub (Aug 28, 2024):

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!

@sickcodes commented on GitHub (Aug 28, 2024): 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!
Author
Owner

@BobH-Official commented on GitHub (Aug 28, 2024):

Wondering is there any plan to change to other registry service is Docker Hub is not working?

@BobH-Official commented on GitHub (Aug 28, 2024): Wondering is there any plan to change to other registry service is Docker Hub is not working?
Author
Owner

@qiqiqiao commented on GitHub (Aug 28, 2024):

mark

@qiqiqiao commented on GitHub (Aug 28, 2024): mark
Author
Owner

@sickcodes commented on GitHub (Aug 28, 2024):

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.

@sickcodes commented on GitHub (Aug 28, 2024): 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.
Author
Owner

@sickcodes commented on GitHub (Aug 30, 2024):

The DMCA notice:

image

@sickcodes commented on GitHub (Aug 30, 2024): The DMCA notice: ![image](https://github.com/user-attachments/assets/8e892547-4605-491f-a320-92161e634cf3)
Author
Owner

@leioukupo commented on GitHub (Aug 30, 2024):

The DMCA notice:

image

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

@leioukupo commented on GitHub (Aug 30, 2024): > The DMCA notice: > > ![image](https://private-user-images.githubusercontent.com/65906298/363050908-8e892547-4605-491f-a320-92161e634cf3.jpeg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ5OTg1NDUsIm5iZiI6MTcyNDk5ODI0NSwicGF0aCI6Ii82NTkwNjI5OC8zNjMwNTA5MDgtOGU4OTI1NDctNDYwNS00OTFmLWEzMjAtOTIxNjFlNjM0Y2YzLmpwZWc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODMwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgzMFQwNjEwNDVaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zMTQ5OWRmOWYyNGVlZjQ3MDIxMjIzZjY3MmEzNzhlMDgwYzZlZGUwNGRiZmM5Y2U3YWM1MjY2MGM3Zjg1YmM1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.oliyfpDxAOyqOgV2j9_NNnSluAAvX920-zXSAzSBgX8) 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
Author
Owner

@Redhawk18 commented on GitHub (Aug 30, 2024):

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.

@Redhawk18 commented on GitHub (Aug 30, 2024): 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.
Author
Owner

@vanderful77 commented on GitHub (Aug 30, 2024):

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.

@vanderful77 commented on GitHub (Aug 30, 2024): 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.
Author
Owner

@Avi0n commented on GitHub (Aug 30, 2024):

I would also backup the this repo by forking it

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.

Apple is not friendly towards open source projects. I would expect to see a dmca from github any day.

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.

@Avi0n commented on GitHub (Aug 30, 2024): > I would also backup the this repo by forking it 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. > Apple is not friendly towards open source projects. I would expect to see a dmca from github any day. 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.
Author
Owner

@KTMGv5 commented on GitHub (Sep 1, 2024):

docker run -it \
--device /dev/kvm \
-p 50922:10022 \
-v /tmp/.X11-unix:/tmp/.X11-unix \
-e "DISPLAY=${DISPLAY:-:0.0}" \
-e GENERATE_UNIQUE=true \
-e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \
registry.cn-hangzhou.aliyuncs.com/shrimp-images/docker-osx:ventura

^^ Corrected

@KTMGv5 commented on GitHub (Sep 1, 2024): ``` docker run -it \ --device /dev/kvm \ -p 50922:10022 \ -v /tmp/.X11-unix:/tmp/.X11-unix \ -e "DISPLAY=${DISPLAY:-:0.0}" \ -e GENERATE_UNIQUE=true \ -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \ registry.cn-hangzhou.aliyuncs.com/shrimp-images/docker-osx:ventura ``` ^^ Corrected
Author
Owner

@leioukupo commented on GitHub (Sep 1, 2024):

docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" -e GENERATE_UNIQUE=true -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' registry.cn-hangzhou.aliyuncs.com/shrimp-images/docker-osx:ventura

Cloning into 'OpenCorePkg'...
fatal: unable to access 'https://github.com/acidanthera/OpenCorePkg.git/': SSL certificate problem: unable to get local issuer certificate

@leioukupo commented on GitHub (Sep 1, 2024): > docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" -e GENERATE_UNIQUE=true -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' [registry.cn-hangzhou.aliyuncs.com/shrimp-images/docker-osx:ventura](http://registry.cn-hangzhou.aliyuncs.com/shrimp-images/docker-osx:ventura) Cloning into 'OpenCorePkg'... fatal: unable to access 'https://github.com/acidanthera/OpenCorePkg.git/': SSL certificate problem: unable to get local issuer certificate
Author
Owner

@HFUT-DY commented on GitHub (Sep 1, 2024):

docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" -e GENERATE_UNIQUE=true -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' registry.cn-hangzhou.aliyuncs.com/shrimp-images/docker-osx:ventura

Cloning into 'OpenCorePkg'... fatal: unable to access 'https://github.com/acidanthera/OpenCorePkg.git/': SSL certificate problem: unable to get local issuer certificate

Maybe you are using a proxy. Type git config --global http.sslVerify false to disable ssl check.

@HFUT-DY commented on GitHub (Sep 1, 2024): > > docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" -e GENERATE_UNIQUE=true -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' [registry.cn-hangzhou.aliyuncs.com/shrimp-images/docker-osx:ventura](http://registry.cn-hangzhou.aliyuncs.com/shrimp-images/docker-osx:ventura) > > Cloning into 'OpenCorePkg'... fatal: unable to access 'https://github.com/acidanthera/OpenCorePkg.git/': SSL certificate problem: unable to get local issuer certificate Maybe you are using a proxy. Type `git config --global http.sslVerify false` to disable ssl check.
Author
Owner

@Polyfish0 commented on GitHub (Sep 2, 2024):

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

@Polyfish0 commented on GitHub (Sep 2, 2024): 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
Author
Owner

@leioukupo commented on GitHub (Sep 2, 2024):

docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" -e GENERATE_UNIQUE=true -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' registry.cn-hangzhou.aliyuncs.com/shrimp-images/docker-osx:ventura

Cloning into 'OpenCorePkg'... fatal: unable to access 'https://github.com/acidanthera/OpenCorePkg.git/': SSL certificate problem: unable to get local issuer certificate

Maybe you are using a proxy. Type git config --global http.sslVerify false to disable ssl check.

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

@leioukupo commented on GitHub (Sep 2, 2024): > > > docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" -e GENERATE_UNIQUE=true -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' [registry.cn-hangzhou.aliyuncs.com/shrimp-images/docker-osx:ventura](http://registry.cn-hangzhou.aliyuncs.com/shrimp-images/docker-osx:ventura) > > > > > > Cloning into 'OpenCorePkg'... fatal: unable to access 'https://github.com/acidanthera/OpenCorePkg.git/': SSL certificate problem: unable to get local issuer certificate > > Maybe you are using a proxy. Type `git config --global http.sslVerify false` to disable ssl check. 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
Author
Owner

@ratnapolepalli commented on GitHub (Sep 2, 2024):

Could we get for Sonoma as well

@ratnapolepalli commented on GitHub (Sep 2, 2024): Could we get for Sonoma as well
Author
Owner

@DevsGrupoCoagro commented on GitHub (Sep 2, 2024):

Alguém conseguiu fazer isso?

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
Unable to find image 'sickcodes/docker-osx:latest' 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'.

@DevsGrupoCoagro commented on GitHub (Sep 2, 2024): > Alguém conseguiu fazer isso? 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 Unable to find image 'sickcodes/docker-osx:latest' 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'.
Author
Owner

@vuanj commented on GitHub (Sep 2, 2024):

@DevsGrupoCoagro dude, just read this thread. the image has been deleted due to DMCA

@vuanj commented on GitHub (Sep 2, 2024): @DevsGrupoCoagro dude, just read this thread. the image has been deleted due to DMCA
Author
Owner

@beeman commented on GitHub (Sep 2, 2024):

@DevsGrupoCoagro dude, just read this thread. the image has been deleted due to DMCA

Is there any solution?

The solution is to read this thread instead of asking randomly.

@beeman commented on GitHub (Sep 2, 2024): > > @DevsGrupoCoagro dude, just read this thread. the image has been deleted due to DMCA > > Is there any solution? The solution is to read this thread instead of asking randomly.
Author
Owner

@voidarclabs commented on GitHub (Sep 2, 2024):

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.

@voidarclabs commented on GitHub (Sep 2, 2024): 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](https://github.com/dockur/macos) that has similar functionality.
Author
Owner

@JulyIghor commented on GitHub (Sep 2, 2024):

Could be DMCA possible because of this?
telegram-cloud-photo-size-2-5382110831464015034-y

@JulyIghor commented on GitHub (Sep 2, 2024): Could be DMCA possible because of this? ![telegram-cloud-photo-size-2-5382110831464015034-y](https://github.com/user-attachments/assets/f91181c1-b4ec-44e1-b60d-98a784c51365)
Author
Owner

@danielchenming commented on GitHub (Sep 3, 2024):

docker run -it \
--device /dev/kvm \
-p 50922:10022 \
-v /tmp/.X11-unix:/tmp/.X11-unix \
-e "DISPLAY=${DISPLAY:-:0.0}" \
-e GENERATE_UNIQUE=true \
-e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \
registry.cn-hangzhou.aliyuncs.com/shrimp-images/docker-osx:ventura

^^ 已更正

@KTMGv5 Do you have a Sonoma version of the image?Looking forward to your reply, thank you!

@danielchenming commented on GitHub (Sep 3, 2024): > ``` > docker run -it \ > --device /dev/kvm \ > -p 50922:10022 \ > -v /tmp/.X11-unix:/tmp/.X11-unix \ > -e "DISPLAY=${DISPLAY:-:0.0}" \ > -e GENERATE_UNIQUE=true \ > -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \ > registry.cn-hangzhou.aliyuncs.com/shrimp-images/docker-osx:ventura > ``` > > ^^ 已更正 @KTMGv5 Do you have a Sonoma version of the image?Looking forward to your reply, thank you!
Author
Owner

@voidarclabs commented on GitHub (Sep 3, 2024):

Could be DMCA possible because of this?

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

@voidarclabs commented on GitHub (Sep 3, 2024): > Could be DMCA possible because of this? @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.
Author
Owner

@osmarjberaldo commented on GitHub (Sep 7, 2024):

docker run -it
--device /dev/kvm
-p 50922:10022
-v /tmp/.X11-unix:/tmp/.X11-unix
-e "DISPLAY=${DISPLAY:-:0.0}"
-e GENERATE_UNIQUE=true
-e RAM=8
-e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist'
dickhub/docker-osx:ventura

@osmarjberaldo commented on GitHub (Sep 7, 2024): docker run -it \ --device /dev/kvm \ -p 50922:10022 \ -v /tmp/.X11-unix:/tmp/.X11-unix \ -e "DISPLAY=${DISPLAY:-:0.0}" \ -e GENERATE_UNIQUE=true \ -e RAM=8 \ -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \ dickhub/docker-osx:ventura
Author
Owner

@EmileHanau commented on GitHub (Sep 7, 2024):

How to get a Sonoma image:

git clone https://github.com/sickcodes/Docker-OSX.git
cd Docker-OSX
docker build -t sickcodes/docker-osx:sonoma --build-arg SHORTNAME=sonoma .

(Applicable for other images as well by editing SHORTNAME and the name of the image in docker build ...)

Explanation:
This clones the repository into a local folder and builds the image locally as @voidarclabs suggested for a "fix". Also this is safer as you shouldn't necessarily trust random strangers docker images.

@EmileHanau commented on GitHub (Sep 7, 2024): **How to get a Sonoma image:** ```bash git clone https://github.com/sickcodes/Docker-OSX.git cd Docker-OSX docker build -t sickcodes/docker-osx:sonoma --build-arg SHORTNAME=sonoma . ``` _(Applicable for other images as well by editing `SHORTNAME` and the name of the image in `docker build ...`)_ **Explanation:** This clones the repository into a local folder and builds the image locally as @voidarclabs suggested for a "fix". Also this is safer as you shouldn't necessarily trust random strangers docker images.
Author
Owner

@jindl1113 commented on GitHub (Sep 8, 2024):

How to get a Sonoma image:

git clone https://github.com/sickcodes/Docker-OSX.git
cd Docker-OSX
docker build -t sickcodes/docker-osx:sonoma --build-arg SHORTNAME=sonoma .

(Applicable for other images as well by editing SHORTNAME and the name of the image in docker build ...)

Explanation: This clones the repository into a local folder and builds the image locally as @voidarclabs suggested for a "fix". Additionally it renames the imnaAlso this is safer as you shouldn't necessarily trust random strangers docker images.

屏幕截图 2024-09-08 181742
@jindl1113 commented on GitHub (Sep 8, 2024): > **How to get a Sonoma image:** > > ```shell > git clone https://github.com/sickcodes/Docker-OSX.git > cd Docker-OSX > docker build -t sickcodes/docker-osx:sonoma --build-arg SHORTNAME=sonoma . > ``` > > _(Applicable for other images as well by editing `SHORTNAME` and the name of the image in `docker build ...`)_ > > **Explanation:** This clones the repository into a local folder and builds the image locally as @voidarclabs suggested for a "fix". Additionally it renames the imnaAlso this is safer as you shouldn't necessarily trust random strangers docker images. <img width="720" alt="屏幕截图 2024-09-08 181742" src="https://github.com/user-attachments/assets/3aabd01b-40c2-40ee-9a16-aa1fce4e98a2">
Author
Owner

@voidarclabs commented on GitHub (Sep 8, 2024):

屏幕截图 2024-09-08 181742

The servers hosting the installer images are probably down. You will need to download your own baseimage and basesystem images. These can be found packages in an installer iso or in an archive somewhere. You'll have to do some searching but if you join the discord I'm sure someone on there can help you out!

@voidarclabs commented on GitHub (Sep 8, 2024): > <img width="720" alt="屏幕截图 2024-09-08 181742" src="https://github.com/user-attachments/assets/3aabd01b-40c2-40ee-9a16-aa1fce4e98a2"> > The servers hosting the installer images are probably down. You will need to download your own baseimage and basesystem images. These can be found packages in an installer iso or in an archive somewhere. You'll have to do some searching but if you join the discord I'm sure someone on there can help you out!
Author
Owner

@osmarjberaldo commented on GitHub (Sep 9, 2024):

acabei de instalar normal tanto ventura e sonoma outros pcs
Captura de tela 2024-09-08 214755
Captura de tela 2024-09-08 223018

@osmarjberaldo commented on GitHub (Sep 9, 2024): acabei de instalar normal tanto ventura e sonoma outros pcs ![Captura de tela 2024-09-08 214755](https://github.com/user-attachments/assets/ccfbc00c-faaf-46dc-aac4-c27d788d4610) ![Captura de tela 2024-09-08 223018](https://github.com/user-attachments/assets/0d507ea8-4025-4df6-b8bf-f762d50dbc70)
Author
Owner

@osmarjberaldo commented on GitHub (Sep 9, 2024):

update code ```
download docker contener seraphix/docker-osx


docker run -it \
--device /dev/kvm \
-p 50922:10022 \
-v /tmp/.X11-unix:/tmp/.X11-unix \
-e "DISPLAY=${DISPLAY:-:0.0}" \
-e GENERATE_UNIQUE=true \
-e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \
seraphix/docker-osx:sonoma
@osmarjberaldo commented on GitHub (Sep 9, 2024): update code ``` download docker contener seraphix/docker-osx ``` docker run -it \ --device /dev/kvm \ -p 50922:10022 \ -v /tmp/.X11-unix:/tmp/.X11-unix \ -e "DISPLAY=${DISPLAY:-:0.0}" \ -e GENERATE_UNIQUE=true \ -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \ seraphix/docker-osx:sonoma
Author
Owner

@donle311093 commented on GitHub (Sep 9, 2024):

Hi all,

I have the another issue build with ventura, the latest of macos 13 is 13.6.9, i try to specific version by "--build-arg VERSION=13.6.1" like example in dockerfile, but after install, it's alway 13.6.9, so I would like to ask this option "--build-arg VERSION=13.6.1" can work?

@donle311093 commented on GitHub (Sep 9, 2024): Hi all, I have the another issue build with ventura, the latest of macos 13 is 13.6.9, i try to specific version by "--build-arg VERSION=13.6.1" like example in dockerfile, but after install, it's alway 13.6.9, so I would like to ask this option "--build-arg VERSION=13.6.1" can work?
Author
Owner

@mateusdata commented on GitHub (Sep 11, 2024):

atualizar código ``` baixar docker contener seraphix/docker-osx


docker run -it \
--device /dev/kvm \
-p 50922:10022 \
-v /tmp/.X11-unix:/tmp/.X11-unix \
-e "DISPLAY=${DISPLAY:-:0.0}" \
-e GENERATE_UNIQUE=true \
-e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \
seraphix/docker-osx:sonoma

Funcionou pra mim, muito obrigado

@mateusdata commented on GitHub (Sep 11, 2024): > atualizar código ``` baixar docker contener seraphix/docker-osx > > ``` > > docker run -it \ > --device /dev/kvm \ > -p 50922:10022 \ > -v /tmp/.X11-unix:/tmp/.X11-unix \ > -e "DISPLAY=${DISPLAY:-:0.0}" \ > -e GENERATE_UNIQUE=true \ > -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \ > seraphix/docker-osx:sonoma > ``` Funcionou pra mim, muito obrigado
Author
Owner

@alejoluc commented on GitHub (Sep 13, 2024):

I find myself in a bind here

update code ``` download docker contener seraphix/docker-osx


docker run -it \
--device /dev/kvm \
-p 50922:10022 \
-v /tmp/.X11-unix:/tmp/.X11-unix \
-e "DISPLAY=${DISPLAY:-:0.0}" \
-e GENERATE_UNIQUE=true \
-e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \
seraphix/docker-osx:sonoma

I get this output:

C:\Users\User\Desktop>docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" -e GENERATE_UNIQUE=true -e CPU='Haswell-noTSX' -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on' -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom-sonoma.plist' sickcodes/docker-osx:sonoma
DEVICE_MODEL:       iMacPro1,1
SERIAL_SET_COUNT:   1
OUTPUT_DIRECTORY:   .
Cloning into 'OpenCorePkg'...
remote: Enumerating objects: 1761, done.
remote: Counting objects: 100% (1761/1761), done.
remote: Compressing objects: 100% (1529/1529), done.
remote: Total 1761 (delta 384), reused 708 (delta 175), pack-reused 0 (from 0)
Receiving objects: 100% (1761/1761), 15.84 MiB | 1.36 MiB/s, done.
Resolving deltas: 100% (384/384), done.
make: Entering directory '/home/arch/OSX-KVM/OpenCorePkg/Utilities/macserial'
cc  Linux_X64/macserial.o Linux_X64/UserPseudoRandom.o  -o macserial
strip -x macserial
make: Leaving directory '/home/arch/OSX-KVM/OpenCorePkg/Utilities/macserial'
  File: ./macserial
  Size: 1045280         Blocks: 2048       IO Block: 4096   regular file
Device: 0,161   Inode: 141019      Links: 1
Access: (0755/-rwxr-xr-x)  Uid: ( 1000/    arch)   Gid: ( 1000/    arch)
Access: 2024-09-12 23:22:22.911356467 +0000
Modify: 2024-09-12 23:22:22.911356467 +0000
Change: 2024-09-12 23:22:22.911356467 +0000
 Birth: 2024-09-12 23:22:22.881355290 +0000
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 2212k  100 2212k    0     0  1193k      0  0:00:01  0:00:01 --:--:-- 1192k
"iMacPro1,1","C02DH0J6HX87","C02040300GUJG36FB","58E37254-7135-42C6-A6F8-EC7A9B00E87C","D0:D2:B0:9F:C1:3F","1920","1080",""
Wrote CSV to: ./serial_sets-2024-09-12-23:22:08.csv
iMacPro1,1      C02DH0J6HX87    C02040300GUJG36FB       58E37254-7135-42C6-A6F8-EC7A9B00E87C    D0:D2:B0:9F:C1:3F      1920     1080
Wrote TSV to: ./serial.tsv
curl: (3) URL rejected: Port number was not a decimal number between 0 and 65535

Same happens if I do, as suggested above:

git clone https://github.com/sickcodes/Docker-OSX.git
cd Docker-OSX
docker build -t sickcodes/docker-osx:sonoma --build-arg SHORTNAME=sonoma .

docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" -e GENERATE_UNIQUE=true -e CPU='Haswell-noTSX' -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on' -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom-sonoma.plist' sickcodes/docker-osx:sonoma
@alejoluc commented on GitHub (Sep 13, 2024): I find myself in a bind here > update code ``` download docker contener seraphix/docker-osx > > ``` > > docker run -it \ > --device /dev/kvm \ > -p 50922:10022 \ > -v /tmp/.X11-unix:/tmp/.X11-unix \ > -e "DISPLAY=${DISPLAY:-:0.0}" \ > -e GENERATE_UNIQUE=true \ > -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \ > seraphix/docker-osx:sonoma > ``` I get this output: ``` C:\Users\User\Desktop>docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" -e GENERATE_UNIQUE=true -e CPU='Haswell-noTSX' -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on' -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom-sonoma.plist' sickcodes/docker-osx:sonoma DEVICE_MODEL: iMacPro1,1 SERIAL_SET_COUNT: 1 OUTPUT_DIRECTORY: . Cloning into 'OpenCorePkg'... remote: Enumerating objects: 1761, done. remote: Counting objects: 100% (1761/1761), done. remote: Compressing objects: 100% (1529/1529), done. remote: Total 1761 (delta 384), reused 708 (delta 175), pack-reused 0 (from 0) Receiving objects: 100% (1761/1761), 15.84 MiB | 1.36 MiB/s, done. Resolving deltas: 100% (384/384), done. make: Entering directory '/home/arch/OSX-KVM/OpenCorePkg/Utilities/macserial' cc Linux_X64/macserial.o Linux_X64/UserPseudoRandom.o -o macserial strip -x macserial make: Leaving directory '/home/arch/OSX-KVM/OpenCorePkg/Utilities/macserial' File: ./macserial Size: 1045280 Blocks: 2048 IO Block: 4096 regular file Device: 0,161 Inode: 141019 Links: 1 Access: (0755/-rwxr-xr-x) Uid: ( 1000/ arch) Gid: ( 1000/ arch) Access: 2024-09-12 23:22:22.911356467 +0000 Modify: 2024-09-12 23:22:22.911356467 +0000 Change: 2024-09-12 23:22:22.911356467 +0000 Birth: 2024-09-12 23:22:22.881355290 +0000 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2212k 100 2212k 0 0 1193k 0 0:00:01 0:00:01 --:--:-- 1192k "iMacPro1,1","C02DH0J6HX87","C02040300GUJG36FB","58E37254-7135-42C6-A6F8-EC7A9B00E87C","D0:D2:B0:9F:C1:3F","1920","1080","" Wrote CSV to: ./serial_sets-2024-09-12-23:22:08.csv iMacPro1,1 C02DH0J6HX87 C02040300GUJG36FB 58E37254-7135-42C6-A6F8-EC7A9B00E87C D0:D2:B0:9F:C1:3F 1920 1080 Wrote TSV to: ./serial.tsv curl: (3) URL rejected: Port number was not a decimal number between 0 and 65535 ``` Same happens if I do, as suggested above: ``` git clone https://github.com/sickcodes/Docker-OSX.git cd Docker-OSX docker build -t sickcodes/docker-osx:sonoma --build-arg SHORTNAME=sonoma . docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY:-:0.0}" -e GENERATE_UNIQUE=true -e CPU='Haswell-noTSX' -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on' -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom-sonoma.plist' sickcodes/docker-osx:sonoma ```
Author
Owner

@kuba-04 commented on GitHub (Sep 13, 2024):

docker run -it
--device /dev/kvm
-p 50922:10022
-v /tmp/.X11-unix:/tmp/.X11-unix
-e "DISPLAY=${DISPLAY:-:0.0}"
-e GENERATE_UNIQUE=true
-e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist'
seraphix/docker-osx:sonoma

Previously it worked (somewhat because the safari was stuck int the loop). But now when running this command I get this:

DEVICE_MODEL: iMacPro1,1
SERIAL_SET_COUNT: 1
OUTPUT_DIRECTORY: .
Cloning into 'OpenCorePkg'...
remote: Enumerating objects: 1761, done.
remote: Counting objects: 100% (1761/1761), done.
remote: Compressing objects: 100% (1529/1529), done.
error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: CANCEL (err 8)
error: 20 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

@kuba-04 commented on GitHub (Sep 13, 2024): > docker run -it \ > --device /dev/kvm \ > -p 50922:10022 \ > -v /tmp/.X11-unix:/tmp/.X11-unix \ > -e "DISPLAY=${DISPLAY:-:0.0}" \ > -e GENERATE_UNIQUE=true \ > -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \ > seraphix/docker-osx:sonoma Previously it worked (somewhat because the safari was stuck int the loop). But now when running this command I get this: DEVICE_MODEL: iMacPro1,1 SERIAL_SET_COUNT: 1 OUTPUT_DIRECTORY: . Cloning into 'OpenCorePkg'... remote: Enumerating objects: 1761, done. remote: Counting objects: 100% (1761/1761), done. remote: Compressing objects: 100% (1529/1529), done. error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: CANCEL (err 8) error: 20 bytes of body are still expected fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: fetch-pack: invalid index-pack output
Author
Owner

@osmarjberaldo commented on GitHub (Sep 13, 2024):

instalou os compontens do linux antes como kvm?

@osmarjberaldo commented on GitHub (Sep 13, 2024): instalou os compontens do linux antes como kvm?
Author
Owner

@kuba-04 commented on GitHub (Sep 13, 2024):

instalou os compontens do linux antes como kvm?

no

@kuba-04 commented on GitHub (Sep 13, 2024): > instalou os compontens do linux antes como kvm? no
Author
Owner

@osmarjberaldo commented on GitHub (Sep 13, 2024):

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
sudo pacman -S qemu libvirt dnsmasq virt-manager bridge-utils flex bison iptables-nft edk2-ovmf

UBUNTU DEBIAN

sudo apt install qemu qemu-kvm libvirt-clients libvirt-daemon-system bridge-utils virt-manager libguestfs-tools

CENTOS RHEL FEDORA

sudo yum install libvirt qemu-kvm
Then, enable libvirt and load the KVM kernel module:

sudo systemctl enable --now libvirtd
sudo systemctl enable --now virtlogd

echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs

sudo modprobe kvm

@osmarjberaldo commented on GitHub (Sep 13, 2024): 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 sudo pacman -S qemu libvirt dnsmasq virt-manager bridge-utils flex bison iptables-nft edk2-ovmf # UBUNTU DEBIAN sudo apt install qemu qemu-kvm libvirt-clients libvirt-daemon-system bridge-utils virt-manager libguestfs-tools # CENTOS RHEL FEDORA sudo yum install libvirt qemu-kvm Then, enable libvirt and load the KVM kernel module: sudo systemctl enable --now libvirtd sudo systemctl enable --now virtlogd echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs sudo modprobe kvm
Author
Owner

@kuba-04 commented on GitHub (Sep 13, 2024):

Thank you @criandoideiasoficial, that indeed helped. Then what to do with this message? What am I missing now?

image

@kuba-04 commented on GitHub (Sep 13, 2024): Thank you @criandoideiasoficial, that indeed helped. Then what to do with this message? What am I missing now? ![image](https://github.com/user-attachments/assets/22337c20-68ea-4ec3-942d-a89051423499)
Author
Owner

@alejoluc commented on GitHub (Sep 14, 2024):

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 taken

In Powershell:

$ git clone https://github.com/sickcodes/Docker-OSX.git
$ cd Docker-OSX
$ docker build -t sickcodes/docker-osx:ventura --build-arg SHORTNAME=ventura .
  • Entered WSL
$ sudo apt-get update
$ sudo apt -y install bridge-utils cpu-checker libvirt-clients libvirt-daemon qemu qemu-kvm
$ sudo apt install x11-apps -y
$ sudo apt install -y tasksel
$ sudo tasksel install xubuntu-desktop
$ sudo apt install gtk2-engines
  • Changed to root user and added these lines
$ sudo su
$ nano ~/.bashrc

export DISPLAY=$(ip route | grep default | awk '{print $3}'):0.0
export LIBGL_ALWAYS_INDIRECT=1
sudo /etc/init.d/dbus start &> /dev/null

$ sudo xhost +local:root`
  • Downloaded https://sourceforge.net/projects/vcxsrv/ and installed
  • Opened XLaunch
  • Chose "Multiple Windows"
  • First screen. Set window number as 0 (didn't test with -1)
  • Next screen. Select "Start no client"
  • Next screen. Ensure all options are checked including "disable access control". Additional parameters: -ac -listen tcp
  • Finish. Allow network access / firewall if prompted.
  • Exited wsl
  • Ran in powershell
$ wsl --update
$ wsl --shutdown
$ wsl
  • Started Docker Desktop
  • Verified correct IP in env var and connection from the Docker container by running in WSL
    $ docker run -it --entrypoint /bin/bash --device /dev/kvm -e "DISPLAY=$DISPLAY" sickcodes/docker-osx:ventura
	* Inside the container shell:
	 $ echo $DISPLAY
	 $ ip route
	 (grab IP from previous command)
	 $ ping -c 4 172.X.X.X
  • Ran in WSL
    $ docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY}" sickcodes/docker-osx:ventura

I did it again to verify all the steps work in this order on my setup. Hope this helps

@alejoluc commented on GitHub (Sep 14, 2024): 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 taken In Powershell: ``` $ git clone https://github.com/sickcodes/Docker-OSX.git $ cd Docker-OSX $ docker build -t sickcodes/docker-osx:ventura --build-arg SHORTNAME=ventura . ``` * Entered WSL ``` $ sudo apt-get update $ sudo apt -y install bridge-utils cpu-checker libvirt-clients libvirt-daemon qemu qemu-kvm $ sudo apt install x11-apps -y $ sudo apt install -y tasksel $ sudo tasksel install xubuntu-desktop $ sudo apt install gtk2-engines ``` * Changed to root user and added these lines ``` $ sudo su $ nano ~/.bashrc ``` > export DISPLAY=$(ip route | grep default | awk '{print $3}'):0.0 > export LIBGL_ALWAYS_INDIRECT=1 > sudo /etc/init.d/dbus start &> /dev/null ``` $ sudo xhost +local:root` ``` * Downloaded https://sourceforge.net/projects/vcxsrv/ and installed * Opened XLaunch * Chose "Multiple Windows" * First screen. Set window number as 0 (didn't test with -1) * Next screen. Select "Start no client" * Next screen. Ensure all options are checked including "disable access control". Additional parameters: -ac -listen tcp * Finish. Allow network access / firewall if prompted. * Exited wsl * Ran in powershell ``` $ wsl --update $ wsl --shutdown $ wsl ``` * Started Docker Desktop * Verified correct IP in env var and connection from the Docker container by running in WSL `$ docker run -it --entrypoint /bin/bash --device /dev/kvm -e "DISPLAY=$DISPLAY" sickcodes/docker-osx:ventura` ``` * Inside the container shell: $ echo $DISPLAY $ ip route (grab IP from previous command) $ ping -c 4 172.X.X.X ``` * Ran in WSL `$ docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY}" sickcodes/docker-osx:ventura` I did it again to verify all the steps work in this order on my setup. Hope this helps
Author
Owner

@kftof commented on GitHub (Sep 15, 2024):

Thanks @alejoluc , this also works on Sonoma.

@kftof commented on GitHub (Sep 15, 2024): Thanks @alejoluc , this also works on Sonoma.
Author
Owner

@ZeroToH3ro commented on GitHub (Sep 16, 2024):

why I always stuck at step macOs Ventura select the disk where you want to install MacOS

@ZeroToH3ro commented on GitHub (Sep 16, 2024): why I always stuck at step macOs Ventura select the disk where you want to install MacOS
Author
Owner

@kftof commented on GitHub (Sep 17, 2024):

To start the system, on AMD processors, you will probably need to add these arguments :
-e CPU='Haswell-noTSX' -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on'

My config : W11, WSL2, Ubuntu 20.04, Docker Desktop, Ryzen 5800X

@kftof commented on GitHub (Sep 17, 2024): To start the system, on AMD processors, you will probably need to add these arguments : `-e CPU='Haswell-noTSX' -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on' ` My config : W11, WSL2, Ubuntu 20.04, Docker Desktop, Ryzen 5800X
Author
Owner

@ZeroToH3ro commented on GitHub (Sep 17, 2024):

To start the system, on AMD processors, you will probably need to add these arguments : -e CPU='Haswell-noTSX' -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on'

My config : W11, WSL2, Ubuntu 20.04, Docker Desktop, Ryzen 5800X

I should add these arguments on this command docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY}" sickcodes/docker-osx:ventura right

@ZeroToH3ro commented on GitHub (Sep 17, 2024): > To start the system, on AMD processors, you will probably need to add these arguments : `-e CPU='Haswell-noTSX' -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on' ` > > My config : W11, WSL2, Ubuntu 20.04, Docker Desktop, Ryzen 5800X I should add these arguments on this command `docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY}" sickcodes/docker-osx:ventura` right
Author
Owner

@thewanderingtraderm commented on GitHub (Sep 18, 2024):

how to install macos sequoia with this

@thewanderingtraderm commented on GitHub (Sep 18, 2024): how to install macos sequoia with this
Author
Owner

@mouadtk commented on GitHub (Sep 18, 2024):

need to install x11-xserver-utils

$ sudo xhost +local:root`
@mouadtk commented on GitHub (Sep 18, 2024): need to install x11-xserver-utils > > ``` > $ sudo xhost +local:root` > ``` >
Author
Owner

@poppop9 commented on GitHub (Sep 21, 2024):

hello,Do you have the image file of the tar package now? If so, can you send me a copy? Thank you

@poppop9 commented on GitHub (Sep 21, 2024): > 链 hello,Do you have the image file of the tar package now? If so, can you send me a copy? Thank you
Author
Owner

@Harsh-007-max commented on GitHub (Sep 25, 2024):

need help idk what is this just need macos ventura working in docker

Saving http://oscdn.apple.com/content/downloads/28/14/042-23155/4rscm4lvp3084gutfgpkwj5eex0yyxmzkt/RecoveryImage/BaseSystem.chunklist to ./BaseSystem.chunklist...
Traceback (most recent call last):
  File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 574, in <module>
    sys.exit(main())
             ^^^^^^
  File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 570, in main
    action_download(args)
  File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 309, in action_download
    cnkpath = save_image(info[INFO_SIGN_LINK], info[INFO_SIGN_SESS], cnkname, args.outdir)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 237, in save_image
    terminalsize = max(os.get_terminal_size().columns - TERMINAL_MARGIN, 0)
                       ^^^^^^^^^^^^^^^^^^^^^^
OSError: [Errno 25] Inappropriate ioctl for device
make: *** [Makefile:10: BaseSystem.dmg] Error 1
The command '/bin/bash -c make     && qemu-img convert BaseSystem.dmg -O qcow2 -p -c BaseSystem.img     && rm ./BaseSystem.dmg' returned a non-zero code: 2
@Harsh-007-max commented on GitHub (Sep 25, 2024): need help idk what is this just need macos ventura working in docker ``` Saving http://oscdn.apple.com/content/downloads/28/14/042-23155/4rscm4lvp3084gutfgpkwj5eex0yyxmzkt/RecoveryImage/BaseSystem.chunklist to ./BaseSystem.chunklist... Traceback (most recent call last): File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 574, in <module> sys.exit(main()) ^^^^^^ File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 570, in main action_download(args) File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 309, in action_download cnkpath = save_image(info[INFO_SIGN_LINK], info[INFO_SIGN_SESS], cnkname, args.outdir) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 237, in save_image terminalsize = max(os.get_terminal_size().columns - TERMINAL_MARGIN, 0) ^^^^^^^^^^^^^^^^^^^^^^ OSError: [Errno 25] Inappropriate ioctl for device make: *** [Makefile:10: BaseSystem.dmg] Error 1 The command '/bin/bash -c make && qemu-img convert BaseSystem.dmg -O qcow2 -p -c BaseSystem.img && rm ./BaseSystem.dmg' returned a non-zero code: 2 ```
Author
Owner

@ghost commented on GitHub (Sep 25, 2024):

need help idk what is this just need macos ventura working in docker

Saving http://oscdn.apple.com/content/downloads/28/14/042-23155/4rscm4lvp3084gutfgpkwj5eex0yyxmzkt/RecoveryImage/BaseSystem.chunklist to ./BaseSystem.chunklist...
Traceback (most recent call last):
  File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 574, in <module>
    sys.exit(main())
             ^^^^^^
  File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 570, in main
    action_download(args)
  File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 309, in action_download
    cnkpath = save_image(info[INFO_SIGN_LINK], info[INFO_SIGN_SESS], cnkname, args.outdir)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 237, in save_image
    terminalsize = max(os.get_terminal_size().columns - TERMINAL_MARGIN, 0)
                       ^^^^^^^^^^^^^^^^^^^^^^
OSError: [Errno 25] Inappropriate ioctl for device
make: *** [Makefile:10: BaseSystem.dmg] Error 1
The command '/bin/bash -c make     && qemu-img convert BaseSystem.dmg -O qcow2 -p -c BaseSystem.img     && rm ./BaseSystem.dmg' returned a non-zero code: 2

also having this issue

@ghost commented on GitHub (Sep 25, 2024): > need help idk what is this just need macos ventura working in docker > > ``` > Saving http://oscdn.apple.com/content/downloads/28/14/042-23155/4rscm4lvp3084gutfgpkwj5eex0yyxmzkt/RecoveryImage/BaseSystem.chunklist to ./BaseSystem.chunklist... > Traceback (most recent call last): > File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 574, in <module> > sys.exit(main()) > ^^^^^^ > File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 570, in main > action_download(args) > File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 309, in action_download > cnkpath = save_image(info[INFO_SIGN_LINK], info[INFO_SIGN_SESS], cnkname, args.outdir) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/home/arch/OSX-KVM/./fetch-macOS-v2.py", line 237, in save_image > terminalsize = max(os.get_terminal_size().columns - TERMINAL_MARGIN, 0) > ^^^^^^^^^^^^^^^^^^^^^^ > OSError: [Errno 25] Inappropriate ioctl for device > make: *** [Makefile:10: BaseSystem.dmg] Error 1 > The command '/bin/bash -c make && qemu-img convert BaseSystem.dmg -O qcow2 -p -c BaseSystem.img && rm ./BaseSystem.dmg' returned a non-zero code: 2 > ``` also having this issue
Author
Owner

@MrCharry commented on GitHub (Sep 26, 2024):

Thank you @criandoideiasoficial, that indeed helped. Then what to do with this message? What am I missing now?

image

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)
error: 930 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output", appreciate for your reply.

@MrCharry commented on GitHub (Sep 26, 2024): > Thank you @criandoideiasoficial, that indeed helped. Then what to do with this message? What am I missing now? > > ![image](https://private-user-images.githubusercontent.com/30311112/367336188-22337c20-68ea-4ec3-942d-a89051423499.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjczMjY0OTAsIm5iZiI6MTcyNzMyNjE5MCwicGF0aCI6Ii8zMDMxMTExMi8zNjczMzYxODgtMjIzMzdjMjAtNjhlYS00ZWMzLTk0MmQtYTg5MDUxNDIzNDk5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTI2VDA0NDk1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTJkOTMzNGZmNDRmNTllNWU0NTRjM2Y0Y2JjMjg0MzY2NThhOGMxZjAzNGFhYWM3NDEzNmQyYTVjODk5OTM2OGUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0._5SKh-QMYsJW1SVodJql6vxXLFniQmEA9kPTTPPMMgI) 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) error: 930 bytes of body are still expected fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: fetch-pack: invalid index-pack output", appreciate for your reply.
Author
Owner

@deadlinecode commented on GitHub (Sep 26, 2024):

If you get the Inappropriate ioctl for device just do the following:

  • Open the file Dockerfile
  • Search for the line that says
    RUN make \
      && qemu-img convert BaseSystem.dmg -O qcow2 -p -c BaseSystem.img \
      && rm ./BaseSystem.dmg
    
  • Insert following above the found line
    RUN sed -i -e 's/os.get_terminal_size().columns/80/g' /home/arch/OSX-KVM/./fetch-macOS-v2.py
    

Thats it
(fyi: @meatpioneer , @Harsh-007-max )

@deadlinecode commented on GitHub (Sep 26, 2024): If you get the `Inappropriate ioctl for device` just do the following: - Open the file `Dockerfile` - Search for the line that says ```dockerfile RUN make \ && qemu-img convert BaseSystem.dmg -O qcow2 -p -c BaseSystem.img \ && rm ./BaseSystem.dmg ``` - Insert following above the found line ```dockerfile RUN sed -i -e 's/os.get_terminal_size().columns/80/g' /home/arch/OSX-KVM/./fetch-macOS-v2.py ``` Thats it (fyi: @meatpioneer , @Harsh-007-max )
Author
Owner

@ghost commented on GitHub (Sep 27, 2024):

error
Stuck here

@ghost commented on GitHub (Sep 27, 2024): ![error](https://github.com/user-attachments/assets/9148c9f6-d19b-4ecd-9b31-50ecaa3c409e) Stuck here
Author
Owner

@Harsh-007-max commented on GitHub (Sep 27, 2024):

docker run -it
--device /dev/kvm
-p 50922:10022
-v /tmp/.X11-unix:/tmp/.X11-unix
-e "DISPLAY=${DISPLAY:-:0.0}"
-e GENERATE_UNIQUE=true
-e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist'
registry.cn-hangzhou.aliyuncs.com/shrimp-images/docker-osx:ventura
i ran this command and got an error

docker: Error response from daemon: error gathering device information while adding custom device "/dev/kvm": no such file or directory.

does anyone know how to solve this one

@Harsh-007-max commented on GitHub (Sep 27, 2024): docker run -it \ --device /dev/kvm \ -p 50922:10022 \ -v /tmp/.X11-unix:/tmp/.X11-unix \ -e "DISPLAY=${DISPLAY:-:0.0}" \ -e GENERATE_UNIQUE=true \ -e MASTER_PLIST_URL='https://raw.githubusercontent.com/sickcodes/osx-serial-generator/master/config-custom.plist' \ registry.cn-hangzhou.aliyuncs.com/shrimp-images/docker-osx:ventura i ran this command and got an error ``` docker: Error response from daemon: error gathering device information while adding custom device "/dev/kvm": no such file or directory. ``` does anyone know how to solve this one
Author
Owner

@selective5296 commented on GitHub (Oct 6, 2024):

I think they might've taken it down again

@selective5296 commented on GitHub (Oct 6, 2024): I think they might've taken it down again
Author
Owner

@reavpC6K commented on GitHub (Oct 9, 2024):

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.

@reavpC6K commented on GitHub (Oct 9, 2024): 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.
Author
Owner

@shunia commented on GitHub (Oct 16, 2024):

By following the exact steps provided by @alejoluc, I'm able to enter the installation screen, but then stuck here:
{9BAF92B8-63EA-437B-9B8E-B6254628E0C1}

I'm looking for fixes to solve this but the solution definitely works, but logs when excuting docker run -it --name docker-osx --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY}" sickcodes/docker-osx:ventura is a little bit confusing when it default to sonoma rather than the provided ventura:

No BaseSystem.img available, downloading sonoma
./fetch-macOS-v2.py --shortname=sonoma
1. High Sierra (10.13)
2. Mojave (10.14)
3. Catalina (10.15)
4. Big Sur (11.7)
5. Monterey (12.6)
6. Ventura (13) - RECOMMENDED
7. Sonoma (14) 
8. Sequoia (15) 
Downloading 696-08090...
@shunia commented on GitHub (Oct 16, 2024): By following the exact steps provided by @alejoluc, I'm able to enter the installation screen, but then stuck here: ![{9BAF92B8-63EA-437B-9B8E-B6254628E0C1}](https://github.com/user-attachments/assets/7cbf9c96-f4ff-4357-a60a-9c8233222a3d) I'm looking for fixes to solve this but the solution definitely works, but logs when excuting `docker run -it --name docker-osx --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY}" sickcodes/docker-osx:ventura` is a little bit confusing when it default to sonoma rather than the provided ventura: ``` No BaseSystem.img available, downloading sonoma ./fetch-macOS-v2.py --shortname=sonoma 1. High Sierra (10.13) 2. Mojave (10.14) 3. Catalina (10.15) 4. Big Sur (11.7) 5. Monterey (12.6) 6. Ventura (13) - RECOMMENDED 7. Sonoma (14) 8. Sequoia (15) Downloading 696-08090... ```
Author
Owner

@rishicodelux commented on GitHub (Oct 17, 2024):

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:
{9BAF92B8-63EA-437B-9B8E-B6254628E0C1}

I'm looking for fixes to solve this but the solution definitely works, but logs when excuting docker run -it --name docker-osx --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY}" sickcodes/docker-osx:ventura is a little bit confusing when it default to sonoma rather than the provided ventura:

No BaseSystem.img available, downloading sonoma
./fetch-macOS-v2.py --shortname=sonoma
1. High Sierra (10.13)
2. Mojave (10.14)
3. Catalina (10.15)
4. Big Sur (11.7)
5. Monterey (12.6)
6. Ventura (13) - RECOMMENDED
7. Sonoma (14) 
8. Sequoia (15) 
Downloading 696-08090...

Originally posted by @shunia in https://github.com/sickcodes/Docker-OSX/issues/799#issuecomment-2416951758
`

@rishicodelux commented on GitHub (Oct 17, 2024): 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: ![{9BAF92B8-63EA-437B-9B8E-B6254628E0C1}](https://github.com/user-attachments/assets/7cbf9c96-f4ff-4357-a60a-9c8233222a3d) I'm looking for fixes to solve this but the solution definitely works, but logs when excuting `docker run -it --name docker-osx --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY}" sickcodes/docker-osx:ventura` is a little bit confusing when it default to sonoma rather than the provided ventura: ``` No BaseSystem.img available, downloading sonoma ./fetch-macOS-v2.py --shortname=sonoma 1. High Sierra (10.13) 2. Mojave (10.14) 3. Catalina (10.15) 4. Big Sur (11.7) 5. Monterey (12.6) 6. Ventura (13) - RECOMMENDED 7. Sonoma (14) 8. Sequoia (15) Downloading 696-08090... ``` _Originally posted by @shunia in https://github.com/sickcodes/Docker-OSX/issues/799#issuecomment-2416951758_ `
Author
Owner

@mpdavison commented on GitHub (Oct 18, 2024):

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.

@mpdavison commented on GitHub (Oct 18, 2024): This might help you, @rishicodelux and @shunia: In addition to @alejoluc's steps, I followed these [additional installation steps](https://github.com/sickcodes/Docker-OSX?tab=readme-ov-file#additional-boot-instructions-for-when-you-are-creating-your-container) (erase a disk), and I was then able to select the disk to install to.
Author
Owner

@Sephrael commented on GitHub (Oct 21, 2024):

anyone found the solution for this disk lock issue

Delete the ~240gb hard drive with disk utility as described above

I'm looking for fixes to solve this but the solution definitely works, but logs when excuting docker run -it --name docker-osx --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY}" sickcodes/docker-osx:ventura is a little bit confusing when it default to sonoma rather than the provided ventura:

No BaseSystem.img available, downloading sonoma
./fetch-macOS-v2.py --shortname=sonoma
1. High Sierra (10.13)
2. Mojave (10.14)
3. Catalina (10.15)
4. Big Sur (11.7)
5. Monterey (12.6)
6. Ventura (13) - RECOMMENDED
7. Sonoma (14) 
8. Sequoia (15) 
Downloading 696-08090...

Originally posted by @shunia in #799 (comment) `

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.
docker run -it --device /dev/kvm -p 52922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY}" -e "SHORTNAME=ventura" sickcodes/docker-osx:ventura

I followed the advice of kftof since I have an AMD processor and added in these arguments. Not sure if it's necessary.
docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY}" -e CPU='Haswell-noTSX' -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on' -e SHORTNAME=ventura sickcodes/docker-osx:ventura

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--
Screenshot 2024-10-21 at 11 37 27 AM

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!

@Sephrael commented on GitHub (Oct 21, 2024): > anyone found the solution for this disk lock issue Delete the ~240gb hard drive with disk utility as described above > > I'm looking for fixes to solve this but the solution definitely works, but logs when excuting `docker run -it --name docker-osx --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY}" sickcodes/docker-osx:ventura` is a little bit confusing when it default to sonoma rather than the provided ventura: > > ``` > No BaseSystem.img available, downloading sonoma > ./fetch-macOS-v2.py --shortname=sonoma > 1. High Sierra (10.13) > 2. Mojave (10.14) > 3. Catalina (10.15) > 4. Big Sur (11.7) > 5. Monterey (12.6) > 6. Ventura (13) - RECOMMENDED > 7. Sonoma (14) > 8. Sequoia (15) > Downloading 696-08090... > ``` > > _Originally posted by @shunia in [#799 (comment)](https://github.com/sickcodes/Docker-OSX/issues/799#issuecomment-2416951758)_ ` 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. `docker run -it --device /dev/kvm -p 52922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY}" -e "SHORTNAME=ventura" sickcodes/docker-osx:ventura` I followed the advice of kftof since I have an AMD processor and added in these arguments. Not sure if it's necessary. `docker run -it --device /dev/kvm -p 50922:10022 -v /tmp/.X11-unix:/tmp/.X11-unix -e "DISPLAY=${DISPLAY}" -e CPU='Haswell-noTSX' -e CPUID_FLAGS='kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on' -e SHORTNAME=ventura sickcodes/docker-osx:ventura` 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-- <img width="755" alt="Screenshot 2024-10-21 at 11 37 27 AM" src="https://github.com/user-attachments/assets/76feba8a-d6ba-4f3f-aedc-23397d71b258"> 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!
Author
Owner

@ismael221 commented on GitHub (Oct 22, 2024):

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.

@ismael221 commented on GitHub (Oct 22, 2024): 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.
Author
Owner

@zryyyy commented on GitHub (Oct 23, 2024):

Is anyone else having the same problem as me? Or can anyone tell me what the cause of this problem is?🥺I tried to change the mirror source but it doesn't work.

 ~/Docker-OSX on  master                                        2m43s
 docker build -t sickcodes/docker-osx:sonoma --build-arg SHORTNAME=sonoma .
[+] Building 36.1s (8/29)                                 docker:default
 => [internal] load build definition from Dockerfile                0.0s
 => => transferring dockerfile: 18.04kB                             0.0s
 => [internal] load metadata for docker.io/library/archlinux:base-  2.4s
 => [auth] library/archlinux:pull token for registry-1.docker.io    0.0s
 => [internal] load .dockerignore                                   0.0s
 => => transferring context: 2B                                     0.0s
 => [ 1/25] FROM docker.io/library/archlinux:base-devel@sha256:f49  0.0s
 => CACHED [ 2/25] RUN perl -i -p -e s/^\#Color/Color$'\n'Parallel  0.0s
 => CACHED [ 3/25] RUN tee /etc/pacman.d/mirrorlist <<< 'Server =   0.0s
 => ERROR [ 4/25] RUN pacman -Sy archlinux-keyring --noconfirm     33.6s
------
 > [ 4/25] RUN pacman -Sy archlinux-keyring --noconfirm     && rm -rf /etc/pacman.d/gnupg     && pacman-key --init     && pacman-key --populate archlinux:
0.329 :: Synchronizing package databases...
33.58 error: failed retrieving file 'extra.db' from geo.mirror.pkgbuild.com : Connection time-out
33.58 error: failed retrieving file 'core.db' from geo.mirror.pkgbuild.com : Connection time-out
33.58 error: failed retrieving file 'core.db' from mirror.rackspace.com : Connection time-out
33.58 error: failed retrieving file 'extra.db' from mirror.rackspace.com : Connection time-out
33.58 error: failed retrieving file 'core.db' from mirror.rackspace.com : Connection time-out
33.58 warning: too many errors from mirror.rackspace.com, skipping for the remainder of this transaction
33.58 error: failed retrieving file 'extra.db' from mirror.rackspace.com : Connection time-out
33.58 error: failed to synchronize all databases (download library error)
33.58  core downloading...
33.58  extra downloading...
------
Dockerfile:77
--------------------
  76 |     # Fixes issue with invalid GPG keys: update the archlinux-keyring package to get the latest keys, then remove and regenerate gnupg keys
  77 | >>> RUN pacman -Sy archlinux-keyring --noconfirm \
  78 | >>>     && rm -rf /etc/pacman.d/gnupg \
  79 | >>>     && pacman-key --init \
  80 | >>>     && pacman-key --populate archlinux
  81 |
--------------------
ERROR: failed to solve: process "/bin/bash -c pacman -Sy archlinux-keyring --noconfirm     && rm -rf /etc/pacman.d/gnupg     && pacman-key --init     && pacman-key --populate archlinux" did not complete successfully: exit code: 1

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 codespace

Go to Codespaces and create a new github codespace

Init and update submodule

You need to init and update the submodule using the following command

git submodule init
git submodule update

Update apt and install Docker

  1. Update package index
sudo apt-get update
  1. Install dependency packages
sudo apt-get install \
    apt-transport-https \
    ca-certificates \
    curl \
    software-properties-common
  1. Add official Docker GPG key
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
  1. Set Docker repo
sudo add-apt-repository \
   "deb [arch=amd64] https://download.docker.com/linux/ubuntu \
   $(lsb_release -cs) \
   stable"
  1. Update package index again
sudo apt-get update
  1. Install Docker CE
sudo apt-get install docker-ce
  1. Verify the Installation
sudo docker --version

Build image

docker build -t sickcodes/docker-osx:latest --build-arg SHORTNAME=sonoma .

Save the image

docker save -o docker-osx.tar sickcodes/docker-osx:latest

Then 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
@zryyyy commented on GitHub (Oct 23, 2024): ~~Is anyone else having the same problem as me? Or can anyone tell me what the cause of this problem is?🥺I tried to change the mirror source but it doesn't work.~~ ```  ~/Docker-OSX on  master   2m43s  docker build -t sickcodes/docker-osx:sonoma --build-arg SHORTNAME=sonoma . [+] Building 36.1s (8/29) docker:default => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 18.04kB 0.0s => [internal] load metadata for docker.io/library/archlinux:base- 2.4s => [auth] library/archlinux:pull token for registry-1.docker.io 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [ 1/25] FROM docker.io/library/archlinux:base-devel@sha256:f49 0.0s => CACHED [ 2/25] RUN perl -i -p -e s/^\#Color/Color$'\n'Parallel 0.0s => CACHED [ 3/25] RUN tee /etc/pacman.d/mirrorlist <<< 'Server = 0.0s => ERROR [ 4/25] RUN pacman -Sy archlinux-keyring --noconfirm 33.6s ------ > [ 4/25] RUN pacman -Sy archlinux-keyring --noconfirm && rm -rf /etc/pacman.d/gnupg && pacman-key --init && pacman-key --populate archlinux: 0.329 :: Synchronizing package databases... 33.58 error: failed retrieving file 'extra.db' from geo.mirror.pkgbuild.com : Connection time-out 33.58 error: failed retrieving file 'core.db' from geo.mirror.pkgbuild.com : Connection time-out 33.58 error: failed retrieving file 'core.db' from mirror.rackspace.com : Connection time-out 33.58 error: failed retrieving file 'extra.db' from mirror.rackspace.com : Connection time-out 33.58 error: failed retrieving file 'core.db' from mirror.rackspace.com : Connection time-out 33.58 warning: too many errors from mirror.rackspace.com, skipping for the remainder of this transaction 33.58 error: failed retrieving file 'extra.db' from mirror.rackspace.com : Connection time-out 33.58 error: failed to synchronize all databases (download library error) 33.58 core downloading... 33.58 extra downloading... ------ Dockerfile:77 -------------------- 76 | # Fixes issue with invalid GPG keys: update the archlinux-keyring package to get the latest keys, then remove and regenerate gnupg keys 77 | >>> RUN pacman -Sy archlinux-keyring --noconfirm \ 78 | >>> && rm -rf /etc/pacman.d/gnupg \ 79 | >>> && pacman-key --init \ 80 | >>> && pacman-key --populate archlinux 81 | -------------------- ERROR: failed to solve: process "/bin/bash -c pacman -Sy archlinux-keyring --noconfirm && rm -rf /etc/pacman.d/gnupg && pacman-key --init && pacman-key --populate archlinux" did not complete successfully: exit code: 1 ``` --- 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 codespace Go to [Codespaces](https://github.com/codespaces) and create a new github codespace #### Init and update submodule You need to init and update the submodule using the following command ```zsh git submodule init git submodule update ``` ### Update apt and install Docker 1. Update package index ```zsh sudo apt-get update ``` 2. Install dependency packages ```zsh sudo apt-get install \ apt-transport-https \ ca-certificates \ curl \ software-properties-common ``` 3. Add official Docker GPG key ```zsh curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - ``` 4. Set Docker repo ```zsh sudo add-apt-repository \ "deb [arch=amd64] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) \ stable" ``` 5. Update package index again ```zsh sudo apt-get update ``` 6. Install Docker CE ```zsh sudo apt-get install docker-ce ``` 7. Verify the Installation ```zsh sudo docker --version ``` ### Build image ```zsh docker build -t sickcodes/docker-osx:latest --build-arg SHORTNAME=sonoma . ``` ### Save the image ```zsh docker save -o docker-osx.tar sickcodes/docker-osx:latest ``` Then you can download the image to your own machine If you want to load the image, just type the command below ```zsh docker load -i /path/to/destination/docker-osx.tar ```
Author
Owner

@mdurini-swisscom commented on GitHub (Oct 24, 2024):

my two cents....maybe an update to the README will be helpful...

@mdurini-swisscom commented on GitHub (Oct 24, 2024): my two cents....maybe an update to the README will be helpful...
Author
Owner

@czzt1 commented on GitHub (Oct 27, 2024):

Is anyone else having the same problem as me? Or can anyone tell me what the cause of this problem is?🥺I tried to change the mirror source but it doesn't work.

 ~/Docker-OSX on  master                                        2m43s
 docker build -t sickcodes/docker-osx:sonoma --build-arg SHORTNAME=sonoma .
[+] Building 36.1s (8/29)                                 docker:default
 => [internal] load build definition from Dockerfile                0.0s
 => => transferring dockerfile: 18.04kB                             0.0s
 => [internal] load metadata for docker.io/library/archlinux:base-  2.4s
 => [auth] library/archlinux:pull token for registry-1.docker.io    0.0s
 => [internal] load .dockerignore                                   0.0s
 => => transferring context: 2B                                     0.0s
 => [ 1/25] FROM docker.io/library/archlinux:base-devel@sha256:f49  0.0s
 => CACHED [ 2/25] RUN perl -i -p -e s/^\#Color/Color$'\n'Parallel  0.0s
 => CACHED [ 3/25] RUN tee /etc/pacman.d/mirrorlist <<< 'Server =   0.0s
 => ERROR [ 4/25] RUN pacman -Sy archlinux-keyring --noconfirm     33.6s
------
 > [ 4/25] RUN pacman -Sy archlinux-keyring --noconfirm     && rm -rf /etc/pacman.d/gnupg     && pacman-key --init     && pacman-key --populate archlinux:
0.329 :: Synchronizing package databases...
33.58 error: failed retrieving file 'extra.db' from geo.mirror.pkgbuild.com : Connection time-out
33.58 error: failed retrieving file 'core.db' from geo.mirror.pkgbuild.com : Connection time-out
33.58 error: failed retrieving file 'core.db' from mirror.rackspace.com : Connection time-out
33.58 error: failed retrieving file 'extra.db' from mirror.rackspace.com : Connection time-out
33.58 error: failed retrieving file 'core.db' from mirror.rackspace.com : Connection time-out
33.58 warning: too many errors from mirror.rackspace.com, skipping for the remainder of this transaction
33.58 error: failed retrieving file 'extra.db' from mirror.rackspace.com : Connection time-out
33.58 error: failed to synchronize all databases (download library error)
33.58  core downloading...
33.58  extra downloading...
------
Dockerfile:77
--------------------
  76 |     # Fixes issue with invalid GPG keys: update the archlinux-keyring package to get the latest keys, then remove and regenerate gnupg keys
  77 | >>> RUN pacman -Sy archlinux-keyring --noconfirm \
  78 | >>>     && rm -rf /etc/pacman.d/gnupg \
  79 | >>>     && pacman-key --init \
  80 | >>>     && pacman-key --populate archlinux
  81 |
--------------------
ERROR: failed to solve: process "/bin/bash -c pacman -Sy archlinux-keyring --noconfirm     && rm -rf /etc/pacman.d/gnupg     && pacman-key --init     && pacman-key --populate archlinux" did not complete successfully: exit code: 1

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 codespace

Go to Codespaces and create a new github codespace

Init and update submodule

You need to init and update the submodule using the following command

git submodule init
git submodule update

Update apt and install Docker

  1. Update package index
sudo apt-get update
  1. Install dependency packages
sudo apt-get install \
    apt-transport-https \
    ca-certificates \
    curl \
    software-properties-common
  1. Add official Docker GPG key
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
  1. Set Docker repo
sudo add-apt-repository \
   "deb [arch=amd64] https://download.docker.com/linux/ubuntu \
   $(lsb_release -cs) \
   stable"
  1. Update package index again
sudo apt-get update
  1. Install Docker CE
sudo apt-get install docker-ce
  1. Verify the Installation
sudo docker --version

Build image

docker build -t sickcodes/docker-osx:latest --build-arg SHORTNAME=sonoma .

Save the image

docker save -o docker-osx.tar sickcodes/docker-osx:latest

Then 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

just edit dockefile,add :

ENV http_proxy=http://host:port
ENV https_proxy=http://host:port

set proxy

@czzt1 commented on GitHub (Oct 27, 2024): > ~Is anyone else having the same problem as me? Or can anyone tell me what the cause of this problem is?🥺I tried to change the mirror source but it doesn't work.~ > > ``` >  ~/Docker-OSX on  master   2m43s >  docker build -t sickcodes/docker-osx:sonoma --build-arg SHORTNAME=sonoma . > [+] Building 36.1s (8/29) docker:default > => [internal] load build definition from Dockerfile 0.0s > => => transferring dockerfile: 18.04kB 0.0s > => [internal] load metadata for docker.io/library/archlinux:base- 2.4s > => [auth] library/archlinux:pull token for registry-1.docker.io 0.0s > => [internal] load .dockerignore 0.0s > => => transferring context: 2B 0.0s > => [ 1/25] FROM docker.io/library/archlinux:base-devel@sha256:f49 0.0s > => CACHED [ 2/25] RUN perl -i -p -e s/^\#Color/Color$'\n'Parallel 0.0s > => CACHED [ 3/25] RUN tee /etc/pacman.d/mirrorlist <<< 'Server = 0.0s > => ERROR [ 4/25] RUN pacman -Sy archlinux-keyring --noconfirm 33.6s > ------ > > [ 4/25] RUN pacman -Sy archlinux-keyring --noconfirm && rm -rf /etc/pacman.d/gnupg && pacman-key --init && pacman-key --populate archlinux: > 0.329 :: Synchronizing package databases... > 33.58 error: failed retrieving file 'extra.db' from geo.mirror.pkgbuild.com : Connection time-out > 33.58 error: failed retrieving file 'core.db' from geo.mirror.pkgbuild.com : Connection time-out > 33.58 error: failed retrieving file 'core.db' from mirror.rackspace.com : Connection time-out > 33.58 error: failed retrieving file 'extra.db' from mirror.rackspace.com : Connection time-out > 33.58 error: failed retrieving file 'core.db' from mirror.rackspace.com : Connection time-out > 33.58 warning: too many errors from mirror.rackspace.com, skipping for the remainder of this transaction > 33.58 error: failed retrieving file 'extra.db' from mirror.rackspace.com : Connection time-out > 33.58 error: failed to synchronize all databases (download library error) > 33.58 core downloading... > 33.58 extra downloading... > ------ > Dockerfile:77 > -------------------- > 76 | # Fixes issue with invalid GPG keys: update the archlinux-keyring package to get the latest keys, then remove and regenerate gnupg keys > 77 | >>> RUN pacman -Sy archlinux-keyring --noconfirm \ > 78 | >>> && rm -rf /etc/pacman.d/gnupg \ > 79 | >>> && pacman-key --init \ > 80 | >>> && pacman-key --populate archlinux > 81 | > -------------------- > ERROR: failed to solve: process "/bin/bash -c pacman -Sy archlinux-keyring --noconfirm && rm -rf /etc/pacman.d/gnupg && pacman-key --init && pacman-key --populate archlinux" did not complete successfully: exit code: 1 > ``` > > 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 codespace > Go to [Codespaces](https://github.com/codespaces) and create a new github codespace > > #### Init and update submodule > You need to init and update the submodule using the following command > > ```shell > git submodule init > git submodule update > ``` > > ### Update apt and install Docker > 1. Update package index > > ```shell > sudo apt-get update > ``` > > 2. Install dependency packages > > ```shell > sudo apt-get install \ > apt-transport-https \ > ca-certificates \ > curl \ > software-properties-common > ``` > > 3. Add official Docker GPG key > > ```shell > curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - > ``` > > 4. Set Docker repo > > ```shell > sudo add-apt-repository \ > "deb [arch=amd64] https://download.docker.com/linux/ubuntu \ > $(lsb_release -cs) \ > stable" > ``` > > 5. Update package index again > > ```shell > sudo apt-get update > ``` > > 6. Install Docker CE > > ```shell > sudo apt-get install docker-ce > ``` > > 7. Verify the Installation > > ```shell > sudo docker --version > ``` > > ### Build image > ```shell > docker build -t sickcodes/docker-osx:latest --build-arg SHORTNAME=sonoma . > ``` > > ### Save the image > ```shell > docker save -o docker-osx.tar sickcodes/docker-osx:latest > ``` > > Then you can download the image to your own machine > > If you want to load the image, just type the command below > > ```shell > docker load -i /path/to/destination/docker-osx.tar > ``` just edit dockefile,add : ENV http_proxy=http://host:port ENV https_proxy=http://host:port set proxy
Author
Owner

@sickcodes commented on GitHub (Oct 28, 2024):

I will have the new DMCA compliant images uploaded shortly (merged https://github.com/sickcodes/Docker-OSX/pull/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.

@sickcodes commented on GitHub (Oct 28, 2024): I will have the new DMCA compliant images uploaded shortly (merged https://github.com/sickcodes/Docker-OSX/pull/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.
Author
Owner

@5E7EN commented on GitHub (Nov 28, 2024):

It appears that the images are back up!
https://hub.docker.com/r/sickcodes/docker-osx

@5E7EN commented on GitHub (Nov 28, 2024): It appears that the images are back up! https://hub.docker.com/r/sickcodes/docker-osx
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Docker-OSX#610