Hendrawan Kuncoro

i was able to provision on M1   though it stopped in this step, probably need to enable new VM framework experimental on docker  but confirmed that docker...

yea, that port 80 is annoying. since mojave, MacOS should allow binding lower ports without lifted privilege https://news.ycombinator.com/item?id=18302380 > Now in 10.14, any application, regardless of the user's privileges, can...

okay one thing that we haven't tried `--debug` and finally i was able to replicate your 80 port conflict issue you had on scaleway. But its because i was having...

so about `detected dubious ownership` i found weird thing, so if i do this manually it works ```bash root@vvv:/srv/provision/extensions/core# sudo -EH -u "vagrant" git pull origin master From https://github.com/Varying-Vagrant-Vagrants/vvv-utilities *...

> Is there a vagrant user in the container that also owns all the mounted folders? all dir in /srv owned by vagrant ``` vagrant@vvv:~$ cd /srv/ vagrant@vvv:/srv$ ls -al...

so turns out in my prev setup there is gitconfig in home vagrant ``` root@vvv:/srv/provision/extensions/core# cat /home/vagrant/.gitconfig [safe] directory = /srv/provision/extensions/core directory = /srv/www/default/dashboard directory = /srv/www/default/opcache-statu directory = /srv/www/default/opcache-status...

so i ran `airsenal_setup_initial_db --clean` and it seems after that, pipeline worked fine

@tomjn totally agree with you, this fork and PR merely a PoC and reference for the future when we actually start to fully support docker -- that if we really...

thanks @tomjn, i'll try to update my repo as per your suggestions

yes for sure