sergeycherepanov / homebrew-docker-virtualbox Goto Github PK

Docker workaround for Ryzentosh (AMD based Hackintosh)

Ruby 20.76% Shell 79.24%

homebrew-docker-virtualbox's Introduction

Homebrew Docker Virtualbox (But not VirtualBox only)

This formula resolves the Docker issue on AMD based MacOS (Ryzentosh). Also can be used on any Mac.

PLEASE READ FIRST THE NOTICE: https://gist.github.com/slykar/e92732be9bf81a71e08068245656d70e?permalink_comment_id=4105556#gistcomment-4105556

Installation

Install Virtualbox from Oracle website

https://www.virtualbox.org/wiki/Downloads.

Please don't forget to remove all previous installations.
This step required only if you want to use VirtualBox driver, otherwise see below how to start with another driver.

Virtualbox 6.1.28+ Note

Due the changes of virtualbox networking, you need to allow docker-machine host in order to use 192.168.99.0/8 network. More Details

Add this line into /etc/vbox/networks.conf

* 192.168.99.0/8

Install the docker-virtualbox via Homebrew

brew tap sergeycherepanov/docker-virtualbox
brew install docker-virtualbox

Configure the docker-virtualbox requirements

WARNING: Only this commands requires root permissions, all next should be run under your user

Ensure the NFS exports file exists

sudo touch /etc/exports

Allow the staff group to configure NFS shares and run the balancer without a password prompt

sudo tee /etc/sudoers.d/docker-machine-nfs <<SUDOERS
%staff ALL=(ALL) NOPASSWD: /sbin/nfsd
%staff ALL=(ALL) NOPASSWD: /bin/cp /etc/nfs.conf /etc/nfs.conf.bak
%staff ALL=(ALL) NOPASSWD: /usr/bin/tee /etc/exports
%staff ALL=(ALL) NOPASSWD: /usr/bin/tee /etc/nfs.conf
%staff ALL=(ALL) NOPASSWD: $(brew --prefix)/opt/docker-virtualbox/bin/gobetween
SUDOERS

Reboot your system to be sure that sudoers applied

Configure the environment

If you didn't install Docker for Mac you can link binaries instead of PATH update

brew link --force --overwrite docker-virtualbox

Otherwise configure the PATH variable

# For the bash
echo "export PATH=\"$(brew --prefix docker-virtualbox)/bin:\$PATH\"" >> ~/.bash_profile
# For the zsh
echo "export PATH=\"$(brew --prefix docker-virtualbox)/bin:\$PATH\"" >> ~/.zshrc

Reload the shell

exec $SHELL

Initialize the docker machine

In the first run according to the permissions policy you need to run it manually and approve permissions.

docker-machine-init initialize

This is will download, create and configure the VirtualBox-based machine if the machine was not configured before. If the machine was created manually this will only set up NFS mount.

Start the docker-virtualbox service

When initialization will be finished you are ready to enable the service

The log file will be always available in /tmp/docker-virtualbox.log.

brew services start docker-virtualbox

Verify installation

Test the Docker by running Nginx

docker run -d -p 8989:80 nginx
curl -v localhost:8989

Additional information

If you don't want to use the VirtualBox as docker-machine driver you need to create a machine manually before initialization by similar command:

docker-machine create --driver generic --generic-ip-address=192.168.24.108 --generic-ssh-user=developer --generic-ssh-key=$HOME/.ssh/id_rsa docker

Please note the docker-machine-nfs plugin supports only Debian based Linux as the target system. For more information read the documentation

Read the log when the docker doesn't work properly

tail -n 1000 -f /tmp/docker-virtualbox.log

SSH connection to the docker-machine

docker-machine ssh docker

To stop the service just run

brew services stop docker-virtualbox

To setup environment for 3rd party tools (ctop as example)

source /tmp/docker-virtualbox.env
source /tmp/docker-virtualbox-machine.env

Known issues

The system won't sleep when the NFS server runs
The port forwarding doesn't work for UDP proto (improvement needed)

homebrew-docker-virtualbox's People

Contributors

Stargazers

Watchers

Forkers

nehbit duck-nukem superkareem adayguerra lyhourchhen lyhour-archieved sthales bassrock semyondmt joshone jasonzj jyotirmaybarman freesfish kwvg djonko hanovo dr3mro dannybastos roman901

homebrew-docker-virtualbox's Issues

An unsolicited brew update broke my docker setup

After a brew update broke my current setup I tried reinstalling but I'm currently stuck. I've looked through the docker-machine-init script but i cant seem to find the error.

~$docker-machine-init initialize
Error: No available formula with the name "docker-machine-nfs-generic"

time out reached when running docker command

❯ docker run -d -p 8989:80 nginx

Waiting while Docker starting...

Default \e[91mThe timeout reached, please verify the vm log for errors: /tmp/docker-virtualbox.log\e[39m

my docker log

===> Virtual machine 'docker' already started
[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 

 NFS already mounted. 
--------------------------------------------

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

 ENJOY high speed mounts :D

--------------------------------------------
===> Starting Gobetween...
---> Gobetween started

===> Configuring port forwarding for alrady running containers...

===> Listen for events...

ryzentosh catalina permission : operation not permitted

what I want to do :
give permission to my storage laravel app

what command i do :
docker exec -it myapp-php-fpm chown -R www-data:www-data /application/myapp/app/storage

error Message :
chown: changing ownership of '/application/myapp/app/storage': Operation not permitted

already done this step

sudo tee /etc/sudoers.d/docker-machine-nfs  <<SUDOERS
%staff ALL=(ALL) NOPASSWD: /sbin/nfsd
%staff ALL=(ALL) NOPASSWD: /bin/cp /etc/nfs.conf /etc/nfs.conf.bak
%staff ALL=(ALL) NOPASSWD: /usr/bin/tee /etc/exports
%staff ALL=(ALL) NOPASSWD: /usr/bin/tee /etc/nfs.conf
%staff ALL=(ALL) NOPASSWD: $(brew --prefix docker-virtualbox)/bin/gobetween
SUDOERS

VirtualBox Network failure with 6.1.30

I am running VirtualBox with the following version 6.1.30 r148432. From what I understand, 6.1.28+ requires /etc/vbox/networks.conf set with the CIDR range for the Host-only Network. I have done so but I keep getting the following:

kprinssu@Mac-Pro ~ $ cat /etc/vbox/networks.conf
192.168.99.0/8
kprinssu@Mac-Pro ~ $ 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
Creating CA: /Users/kprinssu/.docker/machine/certs/ca.pem
Creating client certificate: /Users/kprinssu/.docker/machine/certs/cert.pem
Running pre-create checks...
(docker) Image cache directory does not exist, creating it at /Users/kprinssu/.docker/machine/cache...
(docker) No default Boot2Docker ISO found locally, downloading the latest release...
(docker) Latest release for github.com/boot2docker/boot2docker is v19.03.12
(docker) Downloading /Users/kprinssu/.docker/machine/cache/boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v19.03.12/boot2docker.iso...
(docker) 0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100%
Creating machine...
(docker) Copying /Users/kprinssu/.docker/machine/cache/boot2docker.iso to /Users/kprinssu/.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...

This machine has been allocated an IP address, but Docker Machine could not
reach it successfully.

SSH for the machine should still work, but connecting to exposed ports, such as
the Docker daemon port (usually <ip>:2376), may not work properly.

You may need to add the route manually, or use another related workaround.

This could be due to a VPN, proxy, or host file configuration issue.

You also might want to clear any VirtualBox host only interfaces you are not using.
Checking connection to Docker...
Error creating machine: Error checking the host: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.99.107:2376": dial tcp 192.168.99.107:2376: i/o timeout
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.

It looks like docker-machine cannot connect to the Docker VM. I am not too sure what's going wrong with the configuration here. Attempting to manually add the Host-Only Network results in:

Callee RC: | E_ACCESSDENIED (0x80070005)

some shell codes use gnu-style utils

homebrew-docker-virtualbox/bin/docker-machine-init

Line 52 in 95bffc6

 if [[ $(df --block-size=1073741824 | grep '\/$' | awk '{print $2}') -gt 200 ]]; then 

df of BSD version does not have --block-size option (of GNU version does)
I have not checked if there are more lines like that.

Docker routing configuration

The official Docker app has host.docker.internal to expose the host system's network into hosted containers. Currently, this is not configured with docker-virtualbox as the hostname doesn't resolve to anything.

Would it be possible to set up default networking routing like the official Docker app?

problems when i try to use docker login command

Hi,

first of all, thanks for your nice work.

One question: when i try to use "docker login" command i got this:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x46747f4]

goroutine 1 [running]:
github.com/docker/cli/cli/command.ConfigureAuth(0x5d83180, 0xc00054f790, 0x0, 0x0, 0x0, 0x0, 0x0, 0x5ce7701, 0xc00064ea90, 0xc0005d1968)
/go/src/github.com/docker/cli/cli/command/registry.go:128 +0x44
github.com/docker/cli/cli/command/registry.runLogin(0x5d83180, 0xc00054f790, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/go/src/github.com/docker/cli/cli/command/registry/login.go:123 +0x221
github.com/docker/cli/cli/command/registry.NewLoginCommand.func1(0xc00001b080, 0x6dc30a0, 0x0, 0x0, 0x0, 0x0)
/go/src/github.com/docker/cli/cli/command/registry/login.go:45 +0xca
github.com/docker/cli/vendor/github.com/spf13/cobra.(*Command).execute(0xc00001b080, 0xc0004d5710, 0x0, 0x0, 0xc00001b080, 0xc0004d5710)
/go/src/github.com/docker/cli/vendor/github.com/spf13/cobra/command.go:850 +0x460
github.com/docker/cli/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc00045c2c0, 0xc0004d5710, 0x1, 0x1)
/go/src/github.com/docker/cli/vendor/github.com/spf13/cobra/command.go:958 +0x349
github.com/docker/cli/vendor/github.com/spf13/cobra.(*Command).Execute(...)
/go/src/github.com/docker/cli/vendor/github.com/spf13/cobra/command.go:895
main.runDocker(0xc00054f790, 0x5cea3c0, 0xc0000f2010)
/go/src/github.com/docker/cli/cmd/docker/docker.go:287 +0x1d1
main.main()
/go/src/github.com/docker/cli/cmd/docker/docker.go:298 +0xf1

any ideas?

thanks in advance

Running a VM with VirtualBox

Since I used your method to have docker on my machine, I'm unable to run or create a VM using VirtualBox (6.1.16 r140961 (Qt5.6.3)). Is there a workaround?

after stopping any container the rest of them become not-reachable from the host machine

after stopping any container the rest of them become not-reachable from the host machine.
sometimes it happens without any specific action - they just stop responding from host machine. while containers are still running fine inside VM and can interact between each other.

to replicate:

> docker run -d -p 8990:80 nginx
da1861a59e200fc8ecffff128ba880cf6f4fd720c246b2e8562bf01a9b3a9dcc
> docker run -d -p 8989:80 nginx
1c053364e80b96799e485968336be29dc39fcf7149f69a9f4ed48d7fdb881a0d
> curl -v localhost:8989
*   Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 8989 (#0)
> GET / HTTP/1.1
> Host: localhost:8989
> User-Agent: curl/7.64.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx/1.21.1
< Date: Mon, 23 Aug 2021 15:42:30 GMT
< Content-Type: text/html
< Content-Length: 612
< Last-Modified: Tue, 06 Jul 2021 14:59:17 GMT
< Connection: keep-alive
< ETag: "60e46fc5-264"
< Accept-Ranges: bytes
<
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
    body {
        width: 35em;
        margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif;
    }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
</body>
</html>
* Connection #0 to host localhost left intact
* Closing connection 0

> docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                  NAMES
1c053364e80b        nginx               "/docker-entrypoint.…"   9 seconds ago       Up 8 seconds        0.0.0.0:8989->80/tcp   zen_fermat
da1861a59e20        nginx               "/docker-entrypoint.…"   17 seconds ago      Up 16 seconds       0.0.0.0:8990->80/tcp   ecstatic_euclid

> docker stop da1861a59e20
da1861a59e20
 
> curl -v localhost:8989
*   Trying ::1...
* TCP_NODELAY set
* Connection failed
* connect to ::1 port 8989 failed: Connection refused
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connection failed
* connect to 127.0.0.1 port 8989 failed: Connection refused
* Failed to connect to localhost port 8989: Connection refused
* Closing connection 0
curl: (7) Failed to connect to localhost port 8989: Connection refused

docker-compose fails with mkdir <dir>: file exists

I have the package working well for simple docker commands, but fail to get docker-compose executing. Here is the log.

> docker-compose -f docker-compose.yml run abc-def python manage.py shell_plus


Starting abc-def_database_1             ... error
Starting abc-def_post-watch-database_1 ...
Starting abc-def_elasticsearch6_1       ...
Starting abc-def_redis_1                ...
Starting abc-def_post-watch-database_1 ... done
Starting abc-def_elasticsearch6_1       ... error
tabase/data': mkdir /Users/postm/Documents: file exists
Starting abc-def_post-pelican_1          ...

Starting abc-def_redis_1                ... done
Starting abc-def_post-pelican_1          ... done

ERROR: for database  Cannot start service database: error while creating mount source path '/Users/postm/Documents/GitHub/abc-def/docker/database/data': mkdir /Users/postm/Documents: file exists

ERROR: for elasticsearch6  Cannot start service elasticsearch6: error while creating mount source path '/Users/postm/Documents/GitHub/abc-def/docker/elasticsearch/data': mkdir /Users/postm/Documents: file exists
ERROR: Encountered errors while bringing up the project.

I have followed all the instructions and think everything is set up correctly, unsure if this is a bug or a known limitation.

Network error after docker-machine-init initialize

After setting up the machine, I'm getting the following error:

$ docker run -d -p 8989:80 nginx && curl -v localhost:8989
Unable to find image 'nginx:latest' locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/library/nginx/manifests/latest: Get https://auth.docker.io/token?scope=repository%3Alibrary%2Fnginx%3Apull&service=registry.docker.io: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.
*   Trying 127.0.0.1:8989...
* connect to 127.0.0.1 port 8989 failed: Connection refused
*   Trying ::1:8989...
* connect to ::1 port 8989 failed: Connection refused
* Failed to connect to localhost port 8989 after 4 ms: Connection refused
* Closing connection 0
curl: (7) Failed to connect to localhost port 8989 after 4 ms: Connection refused
$

What can I do to try to resolve this?

file_put_contents(): Exclusive locks are not supported for this stream

I hava a laravel application running with docker and the app is unable to start because of the following error.

Looking around i found the source of the problem, but i'm unable to fixit, since i have no idea how to do this.
Can anyone help me?

`I had the same error, while using NFS to share my code from my developer machine to my Centos server. The problem seems to be that the server tried to access my NFS-shared files using NLM locking by default, so I had to disable locking in my settings. This is done by adding nolock in the NFS options in /etc/fstab

This fixed the issue for me`

machines time out

I tried with the

docker-machine init initialize
➜ ```
This machine has been allocated an IP address, but Docker Machine could not
reach it successfully.

SSH for the machine should still work, but connecting to exposed ports, such as
the Docker daemon port (usually :2376), may not work properly.


2) different driver
docker-machine create --driver generic --generic-ip-address=192.168.24.108 --generic-ssh-user=developer --generic-ssh-key=$HOME/.ssh/id_rsa docker

➜  docker-machine ls

NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
docker generic Timeout


I am running Big Sur

Error: Formula `docker-virtualbox` has not implemented #plist, #service or installed a locatable service file

At step: "Start the docker-virtualbox service", running the command brew services start docker-virtualbox, I get the following error:

Error: Formula docker-virtualbox has not implemented #plist, #service or installed a locatable service file

What I've tried:

Restarting my Ryzentosh;
Running docker-machine-init initialize and then brew services start docker-virtualbox again;

Anyone encountered this before? Any fixes?

My system:

MacOs: Sonoma
Ryzen 3900x
Chipset: X570
Ram 32Gb
GPU: Radeon 6800
Virtualbox version: 6.1

VirtualBox Error on command 'docker-machine-init initialize'

I always get this kind of error when I run the command docker-machine-init initialize

Edited:

I am using the VirtualBox version 7.0.0 from https://www.virtualbox.org/wiki/Downloads

Problem with sudoers

Hi, I followed along the tutorial, but this particular line is breaking sudo:

 %staff ALL=(ALL) NOPASSWD: $(brew --prefix docker-virtualbox)/bin/gobetween

$(brew --prefix docker-virtualbox)/bin/gobetween work on a terminal, though

Add configuration file for resources (cpu count, mem count, disk size..)

Configure NFS ... Operation not permitted

my log:

�[1;34m[INFO] �[0mConfigure NFS ... 
�[0;33m
 !!! Sudo will be necessary for editing /etc/exports !!! �[0m
cat: /etc/exports: No such file or directory
tee: /etc/exports: Operation not permitted

it happened when I make this command:

brew services start docker-virtualbox

getting timeout reached error

I'm getting this error

how can I solve this issue?

Error checking TLS connection

Hi,

Thanks for this package.

However I'm getting an error when executing brew services start docker-virtualbox

I have tried.
docker-machine regenerate-certs docker

And my /etc/vbox/networks.conf looks like below (I had to manually create it as VirtualBox didn't create the folder.

* 10.0.0.0/8 192.168.0.0/16 172.16.0.0/12

# * 0.0.0.0/0 ::/0
* 192.168.99.0/8
192.168.99.0/8

 NFS already mounted.
--------------------------------------------

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

 ENJOY high speed mounts :D

--------------------------------------------
===> Starting Gobetween...
---> Gobetween started
Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.99.100:2376": x509: certificate is valid for 127.0.0.1, 127.0.0.1, ::1, 10.0.2.15, not 192.168.99.100
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.

docker-credential-desktop should be symlinked to docker-credential-osxkeychain

Hello! Thanks for this tap, works great I use it frequently.

When logging into the Docker Registry using docker login, I had to symlink docker-credential-osxkeychain to docker-credential-desktop to get it to work.

Not sure how to add this to a Homebrew recipe or I'd send a PR. :)

machines time out, cannot run docker hello-world

I tried with the

docker-machine init initialize
➜ ```
This machine has been allocated an IP address, but Docker Machine could not
reach it successfully.
SSH for the machine should still work, but connecting to exposed ports, such as
the Docker daemon port (usually :2376), may not work properly.

different driver
docker-machine create --driver generic --generic-ip-address=192.168.24.108 --generic-ssh-user=developer --generic-ssh-key=$HOME/.ssh/id_rsa docker

➜ docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
docker generic Timeout

I am running Big Sur

Docker Virtualbox is in a loop

I've just went through the setup and it seems that the Docker Virtualbox is in a loop.

It keeps going and going. It will only stop when I stop the docker-virtualbox service by running brew services stop docker-virtualbox.

Also, when the service is running and I try to run docker run -d -p 8989:80 nginx, a timeout happens:

The log file is empty though:

How to completly reinstall?

I have the same problem as this issue #12

Tried brew reinstall ... and the remove tool by VirtualBox but when I hit docker-machine-init initialize

error getting state for host docker: machine does not exist
error getting state for host docker: machine does not exist
===> Creating docker machine: docker
Docker machine "docker" already exists

And when I try to run docker it enters a loop.

Fatal Error on Monterey 12.2.1

when I try to execute the "docker run -d -p 8989:80 nginx"
I run into an "timeout reached"
log:

===> Virtual machine 'docker' already started
[INFO] Configuration:

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

[INFO] machine presence ... 			fatal error: runtime: bsdthread_register error

runtime stack:
runtime.throw(0x21240dc, 0x21)
	/usr/local/go/src/runtime/panic.go:596 +0x95 fp=0x7ff7bfeffbb0 sp=0x7ff7bfeffb90
runtime.goenvs()
	/usr/local/go/src/runtime/os_darwin.go:108 +0xa0 fp=0x7ff7bfeffbe0 sp=0x7ff7bfeffbb0
runtime.schedinit()
	/usr/local/go/src/runtime/proc.go:486 +0xa1 fp=0x7ff7bfeffc20 sp=0x7ff7bfeffbe0
runtime.rt0_go(0x7ff7bfeffc58, 0x5, 0x7ff7bfeffc58, 0x0, 0x1000000, 0x5, 0x7ff7bfeffd70, 0x7ff7bfeffd7f, 0x7ff7bfeffd82, 0x7ff7bfeffd8b, ...)
	/usr/local/go/src/runtime/asm_amd64.s:158 +0x183 fp=0x7ff7bfeffc28 sp=0x7ff7bfeffc20

Every command I try e.g.

docker-machine ssh docker
docker-machine-init initialize
brew services start docker-virtualbox

I got the same error

docker-machine: command not found

Could you help me? I got this error when I run this command
docker-machine-init initialize

The result after run the above command

Starting "docker"...
(docker) Check network to re-create if needed...
(docker) Waiting for an IP...
Machine "docker" was started.
Waiting for SSH to be available...
Detecting the provisioner...
Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
vm.max_map_count = 262144
[INFO] Configuration:

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

[INFO] machine presence ... 			/usr/local/opt/docker-machine-nfs/bin/docker-machine-nfs: line 239: docker-machine: command not found```

docker-credential-desktop error

I think it's missing the link to docker-credential-desktop. I tried to pull mariadb and got the error:

dockerpycreds.errors.InitializationError: docker-credential-desktop not installed or not available in PATH

So was fixed by:

ln -s "/Applications/Docker.app/Contents/Resources/bin/docker-credential-desktop" /usr/local/bin/docker-credential-desktop

Localhost error

Hi there, thank you guys for all your work, Im noob in hackintosh, I followed the guide step by step but i got this error.

Unable to query docker version

docker-machine errror
Unable to query docker version: Get "https://192.168.99.100:2376/v1.15/version": x509: certificate is valid for 127.0.0.1, 127.0.0.1, ::1, 10.0.2.15, not 192.168.99.100

I solved in this way:

docker-machine regenerate-certs docker

Ventura support

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

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

add info on documentation to allow virtual box in security settings

I got this error when trying to init the machine:
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

turns out it's because I didn't allow virtualbox in security settings