# Big Sur (11.0.1 (20B29))

**URL:** https://discourse.roots.io/t/big-sur-11-0-1-20b29/19510
**Category:** trellis
**Created:** 2020-11-13T11:49:45Z
**Posts:** 26

## Post 1 by @alexkerber — 2020-11-13T11:49:45Z

vagrant version  
vagrant plugin list  
uname -a  
sw\_vers

Installed Version: 2.2.13  
Latest Version: 2.2.13

You’re running an up-to-date version of Vagrant!  
vagrant-bindfs (1.1.8, global)

- Version Constraint: \> 0  
vagrant-hostmanager (1.8.9, global)
- Version Constraint: \> 0  
Darwin alexMACBOOKPRO 20.1.0 Darwin Kernel Version 20.1.0: Sat Oct 31 00:07:11 PDT 2020; root:xnu-7195.50.7~2/RELEASE\_X86\_64 x86\_64  
ProductName: macOS  
ProductVersion: 11.0.1  
BuildVersion: 20B29

## Fails with vagrant up/provision: TASK [wordpress-install : Install Dependencies with Composer] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* System info: Ansible 2.8.0; Vagrant 2.2.13; Darwin Trellis version (per changelog): “Remove default Vagrant SMB credentials”

Composer could not find a composer.json file in  
/srv/www/projectname.com/current To initialize a project, please create a  
composer.json file as described in the [https://getcomposer.org/](https://getcomposer.org/) “Getting  
Started” section  
failed: [default] ([item=projectname.com](http://item=projectname.com)) =\> {“ansible\_loop\_var”: “item”, “changed”: false, “item”: {“key”: “[projectname.com](http://projectname.com)”, “value”: {“admin\_email”: “master@admin.test”, “cache”: {“enabled”: false}, “env”: {“acf\_pro\_key”: “”, “domain\_current\_site”: “projectname.test”}, “local\_path”: “…/site”, “multisite”: {“enabled”: false}, “site\_hosts”: [{“canonical”: “projectname.test”, “redirects”: [“www.projectname.test”]}], “ssl”: {“enabled”: false, “provider”: “self-signed”}}}, “stdout”: “Composer could not find a composer.json file in /srv/www/projectname.com/current\nTo initialize a project, please create a composer.json file as described in the [https://getcomposer.org/](https://getcomposer.org/) “Getting Started” section\n”, “stdout\_lines”: [“Composer could not find a composer.json file in /srv/www/projectname.com/current”, “To initialize a project, please create a composer.json file as described in the [https://getcomposer.org/](https://getcomposer.org/) “Getting Started” section”]}

Should we wait for a new vagrant version or VB?

---

## Post 2 by @strarsis — 2020-11-13T13:18:00Z

So the mount of the WordPress sites into the Vagrant Trellis VM failed, hence it cannot find a composer.json of a Bedrock site to proceed? Are synced folders working at all on that system?

---

## Post 3 by @alexkerber — 2020-11-13T13:32:46Z

I think that’s the issue. Vagrant can’t link the folders. Everything in /srv/www/domain.com is there (current/ logs/ shared/) but they are all empty specially current / web.

---

## Post 4 by @Freshcode — 2020-11-13T15:57:44Z

I’m experiencing the same with the following setup:

- MacOS Big Sur (11.0.1)
- Vagrant 2.2.13
- vagrant-bindfs (1.1.8, global)
- vagrant-hostmanager (1.8.9, global)
- vagrant-trellis-cert (0.5.2, global)
- vagrant-trellis-sequel (0.2.2, global)
- Ansible 2.9.15
- VirtualBox 6.1.16 r140961
- Trellis 1.7.0

The path of my Trellis directory is /Users/davevanhoorn/\*\*\*\*\*.nl/server and I granted nfsd Full Disk Access in Security and Privacy settings. This also didn’t help.

---

## Post 5 by @strarsis — 2020-11-13T16:13:29Z

Minimal test Vagrantfile:

```
Vagrant.configure("2") do |config|
  config.vm.box = "bento/ubuntu-20.04"
  config.vm.box_version = ">= 201807.12.0"

  config.vm.synced_folder "src/", "/srv/website"
end
```

When NFS should be used on OSX, some setup is required, see

> **[NFS - Synced Folders | Vagrant by HashiCorp](https://www.vagrantup.com/docs/synced-folders/nfs#prerequisites)**
>
> In some cases the default shared folder implementations such as VirtualBox
> shared folders have high performance penalties. If you are seeing less than
> ideal performance with synced folders, NFS can offer a solution. Vagrant has
> built-in support to...

---

## Post 6 by @Freshcode — 2020-11-13T20:14:22Z

Thanks @strarsis for the minimal test. I replaced the Vagrantfile in the root Trellis directory and that seemed to work, so I figured it’s something with the Trellis setup.

I changed `vagrant_mount_type` in `vagrant.default.yml` and it’s working again. It’s defaulting to `nfs` ([added in this commit](https://github.com/roots/trellis/commit/63cf66fd4701309ee972b31d5505c3c9289e723a#diff-0c08b1985b27e7942e17ee6f8c3bee9946cdc7cc09e9a65bdb28318e99b1c41d)), but that isn’t working for me.

Before:  
`vagrant_mount_type: "nfs"`

After:  
`vagrant_mount_type: "virtualbox"`

I can work again :grinning:

---

## Post 7 by @strarsis — 2020-11-13T20:35:16Z

Glad to hear that. And yes, the `nfs` mount type in Vagrant requires [additional installation and setup in OSX](https://www.vagrantup.com/docs/synced-folders/nfs#prerequisites) before it can be used.

---

## Post 8 by @alexkerber — 2020-11-13T22:47:13Z

It runs but I’m just getting 502 (bad gateway). You can launch the \*.test URL?

---

## Post 9 by @Freshcode — 2020-11-13T23:01:58Z

Yes, everything is up and running again. Do you see the files and folders when you `vagrant ssh` into the local server and check the `srv/www/*.test` directory?

Ps. I had to do a `vagrant destroy` and `vagrant up --provision` before I had it working again.

Ps2. I also had to run the command `vagrant hostmanager` because the servers IP wasn’t showing in my `etc/hosts` file

---

## Post 10 by @alexkerber — 2020-11-14T06:18:38Z

vagrant hostmanager did the trick! thanks!

---

## Post 11 by @alexkerber — 2020-11-14T10:37:51Z

Now I get really bad performance issues. Anyone that expiring the same here?

---

## Post 12 by @strarsis — 2020-11-14T11:07:37Z

Are you currently using NFS for the synced folders, or SMB?

---

## Post 13 by @alexkerber — 2020-11-14T11:42:06Z

> [@Freshcode](#):
>
> virtualbox

virtualbox that Freshcode is using

---

## Post 14 by @amirook — 2020-11-15T22:16:27Z

> [@Freshcode](#):
>
> vagrant\_mount\_type: “virtualbox”

Hi everyone. That fix also worked for me! But I also hat to do _ **vagrant hostmanager** _ Thank you.

But before the “Big Sur” Update and switching the vagrant\_mount\_type I was able to run _ **vargant up** _ for different projects with no problem.  
Now only the first VM I execute _ **vagrant hostmanager** _ on will work. The others boot up without an error, but the browser won’t find anything under the local address.  
Only after I destroy all VMs and remove ~/.vagrant.d/ it works for that first VM I do _ **vagrant hostmanager** _ on.

Is this somehow connected to the change of _vagrant\_mount\_type_?

I also tried to switch it back and give nfs the needed permissions.

> [@Freshcode](#):
>
> vagrant\_mount\_type: “nfs”

But this resulted to the original problem. What am I missing?

---

## Post 15 by @strarsis — 2020-11-16T00:31:43Z

> [@amirook](#):
>
> What am I missing?

Have you set up your OS X system for NFS?

> **[NFS - Synced Folders | Vagrant | HashiCorp Developer](https://developer.hashicorp.com/vagrant/docs/synced-folders/nfs)**
>
> In some cases the default shared folder implementations such as VirtualBox
> shared folders have high performance penalties. If you are seeing less than
> ideal performance with synced folders, NFS can offer a solution. Vagrant has
> built-in support to...

Note the section starting with [‘For OS X, sudoers should have this entry:’](https://www.vagrantup.com/docs/synced-folders/nfs#:~:text=For%20OS%20X,%20sudoers%20should%20have%20this%20entry).

---

## Post 16 by @amirook — 2020-11-16T07:14:59Z

Isn’t there a way to get the routing fixed with mount\_type VirtualBox?  
I use trellis, so I don’t have to worry about vagrant’s and other configurations.

The strange thing is, it used to work when I followed all the steps in the trellis docs.

> [@strarsis](#):
>
> Note the section starting with [‘For OS X, sudoers should have this entry:’](https://www.vagrantup.com/docs/synced-folders/nfs#:~:text=For%20OS%20X,%20sudoers%20should%20have%20this%20entry)

The Link doesn’t reference a specific entry.

---

## Post 17 by @strarsis — 2020-11-16T07:55:29Z

> For OS X, sudoers should have this entry:
> 
> ```
> Cmnd_Alias VAGRANT_EXPORTS_ADD = /usr/bin/tee -a /etc/exports
> Cmnd_Alias VAGRANT_NFSD = /sbin/nfsd restart
> Cmnd_Alias VAGRANT_EXPORTS_REMOVE = /usr/bin/sed -E -e /*/ d -ibak /etc/exports
> %admin ALL=(root) NOPASSWD: VAGRANT_EXPORTS_ADD, VAGRANT_NFSD, VAGRANT_EXPORTS_REMOVE
> ```

---

## Post 18 by @alexkerber — 2020-11-16T08:09:14Z

Thanks for this! Where and what file should this be added?

---

## Post 19 by @strarsis — 2020-11-16T11:20:37Z

> For \*nix users, make sure to edit your `/etc/sudoers` file with `visudo`

---

## Post 20 by @oxyc — 2020-11-17T01:48:25Z

Just a note from a Drupal VM user. I experienced the same issue with vagrant-hostmanager and downgrading from Vagrant 2.2.13 to 2.2.10 fixed it.

> <https://github.com/hashicorp/vagrant/issues/12035>
>
> We use vagrant-disksize plugin to automatically resize the main disk on provision. This has been working fine up until we upgraded...

---

## Post 21 by @disc — 2020-11-18T16:51:44Z

@oxyc : Many thanks! I’ve spend some hours trying to solve this issue…

I’m on Arch Linux. Vagrant is the culprit.

Downgraded to 2.2.10, destroyed the Vagrant VM and recreated it without the error.

Wait until Vagrant 2.2.14 is released.

---

## Post 22 by @alexkerber — 2020-11-22T15:27:22Z

Vagrant 2.2.14 can now be downloaded!

---

## Post 23 by @joshb — 2020-12-18T03:08:21Z

Picked up a newer mac and got it all up to date with Big Sur.

Running all the latest and greatest offerings from all the required tools for a trellis project but I am running into some issues. Luckily I still have my old macbook to get work done while I attempt to get past the issues here on this new one.

I cloned down a previous project and ran vagrant up without any issues.  
Attempting to visit the local dev url and its says unable to connect.

Attempting to re provision and I get the following message:

```
ERROR! couldn't resolve module/action 'ipify_facts'. This often indicates a misspelling, missing collection, or incorrect module path.

The error appears to be in '/Users/joshb/Documents/_development/_trellis/trellis.project.build/trellis/roles/common/tasks/main.yml': line 153, column 7, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

- block:
    - name: Retrieve SSH client IP
      ^ here
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
```

I found this discussion but it did not help.

> [@No response from Ipify](https://discourse.roots.io/t/no-response-from-ipify/9591):
>
> I’m attempting to provision my staging server with ansible-playbook server.yml -e env=staging but I keep getting this message. TASK [common : Retrieve SSH client IP] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* Using module file /usr/local/lib/python2.7/site-packages/ansible/modules/network/ipify\_facts.py \<remote\_ip\> ESTABLISH LOCAL CONNECTION FOR USER: \<local\_username\> \<remote\_ip\> EXEC /bin/sh -c '/usr/bin/python && sleep 0' System info: Ansible 2.…

Is anyone using Big Sur yet and run into any issues? I haven’t been able to find much information about Roots and Big Sur.

---

## Post 24 by @joshb — 2020-12-18T18:32:35Z

Still at it here.  
This is the only relevant similar issue I am able to discover:

> [@No response from Ipify](https://discourse.roots.io/t/no-response-from-ipify/9591):
>
> I’m attempting to provision my staging server with ansible-playbook server.yml -e env=staging but I keep getting this message. TASK [common : Retrieve SSH client IP] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* Using module file /usr/local/lib/python2.7/site-packages/ansible/modules/network/ipify\_facts.py \<remote\_ip\> ESTABLISH LOCAL CONNECTION FOR USER: \<local\_username\> \<remote\_ip\> EXEC /bin/sh -c '/usr/bin/python && sleep 0' System info: Ansible 2.…

I have followed @fullyint’s instructions but it’s not helping.  
Does anyone know what the issue may be?

---

## Post 25 by @joshb — 2020-12-19T03:21:09Z

I managed to figure this out. I believe I had installed node via brew vs pip and when attempting to change versions via nvm it remained stuck at version 10 until I uninstalled it all together and reinstalled via pip.

---

## Post 26 by @system — 2020-12-25T11:59:23Z

This topic was automatically closed after 42 days. New replies are no longer allowed.