search

sergeycherepanov / homebrew-docker-virtualbox

Docker workaround for Ryzentosh (AMD based Hackintosh)
209 stars 20 forks source link

Ventura support #36

Open kdta91 opened 2 years ago

kdta91 commented 2 years ago

Docker doesn't run anymore on Ventura. I suppose that VirtualBox isn't compatible with Ventura.

krisamp@Mac-Pro ~ % docker Waiting while Docker starting...

sergeycherepanov commented 2 years ago

@kdta91 do you able to run the Virtualbox VM directly?

minhhq-nt commented 2 years ago

Hey guys, its a bug from VirtualBox: https://forums.virtualbox.org/viewtopic.php?f=8&t=107571. Guess we will need to wait until its got fixed or we need to back to Monterey and VirtualBox 6.1

kdta91 commented 2 years ago

@sergeycherepanov Virtualbox does open but the VM doesn't work. It could be related as to what @minhhq-nt pointed out. I'm also playing around to fix the issue if it's only on my setup.

oscarpedrero commented 1 year ago

@sergeycherepanov Any news on this?

In Ventura with VB7.0.6 it keeps failing, if we go downgrade to version VB6.1 executing the permissions by hand and approving it in the Security section it works.

Starting "docker"...
(docker) Check network to re-create if needed...
(docker) Creating a new host-only adapter produced an error: /usr/local/bin/VBoxManage hostonlyif create failed:
(docker) 0%...NS_ERROR_FAILURE
(docker) VBoxManage: error: Failed to create the host-only adapter
(docker) VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
(docker) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
(docker) VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 105 of file VBoxManageHostonly.cpp
(docker) 
(docker) This is a known VirtualBox bug. Let's try to recover anyway...
Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue

In Ventura with VB7.0.6 it keeps failing, if we go downgrade to version VB6.1 executing the permissions by hand and approving it in the Preferences - Security section it works.

$ sudo kextload -b org.virtualbox.kext.VBoxDrv
sudo kextload -b org.virtualbox.kext.VBoxNetFlt
sudo kextload -b org.virtualbox.kext.VBoxNetAdp
sudo kextload -b org.virtualbox.kext.VBoxUSB

$ docker-machine-init initialize

Docker machine "docker" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
Docker machine "docker" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
===> Creating docker machine: docker
Running pre-create checks...
Creating machine...
(docker) Copying /Users/developer/.docker/machine/cache/boot2docker.iso to /Users/developer/.docker/machine/machines/docker/boot2docker.iso...
(docker) Creating VirtualBox VM...
(docker) Creating SSH key...
(docker) Starting the VM...
(docker) Check network to re-create if needed...
(docker) Waiting for an IP...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: /usr/local/opt/docker-machine/bin/docker-machine env docker
vm.max_map_count = 262144
[INFO] Configuration:

    - Machine Name: docker 
    - Shared Folder: /Users 
    - Mount Options: noacl,async,nfsvers=3 
    - Force: false 

[INFO] machine presence ...             OK 
[INFO] machine running ...          OK 
[INFO] Lookup mandatory properties ...      OK 

    - Machine IP: 192.168.99.103 
    - Network ID: vboxnet3 
    - NFSHost IP: 192.168.99.1 

[INFO] Configure NFS ... 

 !!! Sudo will be necessary for editing /etc/exports !!! 
                        OK 
[INFO] Configure Docker Machine ...         OK 
[INFO] Restart Docker Machine ...       OK 
[INFO] Verify NFS mount ...             OK 
--------------------------------------------

 The docker-machine 'docker'
 is now mounted with NFS!

 ENJOY high speed mounts :D

--------------------------------------------

>>>>>  *** CONGRATULATION *** DOCKER READY TO USE *** <<<<<
minhhq-nt commented 1 year ago

@sergeycherepanov Any news on this?

In Ventura with VB7.0.6 it keeps failing, if we go downgrade to version VB6.1 executing the permissions by hand and approving it in the Security section it works.

Starting "docker"...
(docker) Check network to re-create if needed...
(docker) Creating a new host-only adapter produced an error: /usr/local/bin/VBoxManage hostonlyif create failed:
(docker) 0%...NS_ERROR_FAILURE
(docker) VBoxManage: error: Failed to create the host-only adapter
(docker) VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
(docker) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
(docker) VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 105 of file VBoxManageHostonly.cpp
(docker) 
(docker) This is a known VirtualBox bug. Let's try to recover anyway...
Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue

In Ventura with VB7.0.6 it keeps failing, if we go downgrade to version VB6.1 executing the permissions by hand and approving it in the Preferences - Security section it works.

$ sudo kextload -b org.virtualbox.kext.VBoxDrv
sudo kextload -b org.virtualbox.kext.VBoxNetFlt
sudo kextload -b org.virtualbox.kext.VBoxNetAdp
sudo kextload -b org.virtualbox.kext.VBoxUSB

$ docker-machine-init initialize

Docker machine "docker" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
Docker machine "docker" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
===> Creating docker machine: docker
Running pre-create checks...
Creating machine...
(docker) Copying /Users/developer/.docker/machine/cache/boot2docker.iso to /Users/developer/.docker/machine/machines/docker/boot2docker.iso...
(docker) Creating VirtualBox VM...
(docker) Creating SSH key...
(docker) Starting the VM...
(docker) Check network to re-create if needed...
(docker) Waiting for an IP...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with boot2docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Checking connection to Docker...
Docker is up and running!
To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: /usr/local/opt/docker-machine/bin/docker-machine env docker
vm.max_map_count = 262144
[INFO] Configuration:

  - Machine Name: docker 
  - Shared Folder: /Users 
  - Mount Options: noacl,async,nfsvers=3 
  - Force: false 

[INFO] machine presence ...           OK 
[INFO] machine running ...            OK 
[INFO] Lookup mandatory properties ...        OK 

  - Machine IP: 192.168.99.103 
  - Network ID: vboxnet3 
  - NFSHost IP: 192.168.99.1 

[INFO] Configure NFS ... 

 !!! Sudo will be necessary for editing /etc/exports !!! 
                      OK 
[INFO] Configure Docker Machine ...       OK 
[INFO] Restart Docker Machine ...         OK 
[INFO] Verify NFS mount ...           OK 
--------------------------------------------

 The docker-machine 'docker'
 is now mounted with NFS!

 ENJOY high speed mounts :D

--------------------------------------------

>>>>>  *** CONGRATULATION *** DOCKER READY TO USE *** <<<<<

Oh did you run VB6.1 on Ventura? I have tried to install VB6.1 on Ventura but no luck. Could you please share how to do it? Btw I got bad news for ryzentosh on Ventura. Seem VB7 gonna use Apples Hypervison so its not gonna work on Ventura with ryzentosh.

MrPitonych commented 1 year ago

docker-machine --debug regenerate-certs -f docker it works for me