New Macbook with M2 Pro Chip

trellis
1

I finally picked myself up a new Macbook with the M2 Pro Chip and so far I am pretty thrilled with the processing power of this thing. I am finally able to successfully use my Apple TV to use my 2nd 4k display without any lag, which is pretty slick.

Now I’ll be preparing to setup some projects on the new machine and I reached out to @ben to ask a few questions but lets talk more about it here…

You’ll need Parallels if you’ve gotta run Vagrant for Trellis

You could also ignore Parallels/Vagrant and just use Lima instead, but Lima isn’t very stable right now, despite it being much faster/nicer to use when it doesn’t have problems. I run into problems with it almost daily, so I can’t 100% recommend it for most client work

So, this is a first for me ever using Parallels. Do I need to download and purchase a copy of Windows 11 as well or just follow the 3 simple steps here for use with Parallels to get started?

Any other issues I should be concerned about before diving too deep into setting up the new machine?

2

Congrats on the new machine. Before you shell out for Parallels, give Lima a try. It’s experimental still, but it’s much faster than Parallels.

No, you don’t need to buy a copy of Windows; just a copy of Parallels Desktop Pro and the appropriate Vagrant provider packages

3

I’m using Lima exclusively and it’s quite buggy for me, so if you need to get work done I’d stick with Parallels for now. It’s quite annoying to fiddle to get Lima back running if it suddenly stops working.

1 Like
4

That is what Ben suggested as well, so that is where I am at now. I am attempting to boot up a project and am receiving this message in my terminal:

There was an error while command execution. The command and stderr is shown below.

Command: ["/usr/local/bin/prlctl", "start", "6cd3f782-60e7-4bea-ac23-dcbe36f21add"]

Stderr: Failed to start the VM: Unable to start "projectname" because your Mac is equipped with the Apple M series chip that does not support Intel-based operating systems. To create a compatible virtual machine, use an ISO or VHDX image file with an ARM-based operating system.

Plus this on Parallels:

image
image2408×446 64.4 KB

5

Got a little bit further booting the project after updating vagrantfile with these lines:

vagrant_box: ‘jeffnoxon/ubuntu-20.04-arm64’

vagrant_box_version: ‘>= 1.0.1’

But met with another error:

There was an error while command execution. The command and stderr is shown below.

Command: ["/usr/local/bin/prlctl", "start", "33976ab3-a21e-4567-a485-7d0c4a93a80a"]

Stderr: Failed to start the VM: The virtual machine cannot be started due to a critical error. 

exit status 1
6

If you’re digging into the Trellis issue, it’s probably better to ignore that entirely and reference Trellis itself since there’s been several PR’s that add support for Apple Silicon such as https://github.com/roots/trellis/pull/1431/files

Are you able to reproduce this issue on a new Trellis install instead of an existing project? It has had support out of the box for Apple Silicon for a while now

7

Ok, so on a brand new trellis install, this is what happens straight up.

✔ example.com
Initializing project...

[✓] Created virtualenv 
[✓] Ensure pip is up to date
[✓] Dependencies installed
Error while installing Ansible Galaxy roles:
ERROR: Ansible could not initialize the preferred locale: unsupported locale setting

This may be a temporary network issue. Please try again.

Attempting to use Lima on the brand new trellis with trellis vm start

Updating /etc/hosts file (sudo may be required, see `trellis vm sudoers` for more details)
Password:

Provisioning VM...
Error while installing Ansible Galaxy roles:
ERROR: Ansible could not initialize the preferred locale: unsupported locale setting

This may be a temporary network issue. Please try again.
Running command => ansible-playbook dev.yml --inventory-file=/Users/joshb/_Development/_Trellis/examples/example.com/trellis/.trellis/lima/inventory -e env=development
ERROR: Ansible could not initialize the preferred locale: unsupported locale setting
exit status 1

On an existing project, using Lima, I am getting further but stuck here currently:

TASK [sshd : Create a secure sshd_config] **************************************
System info:
  Ansible 2.12.10; Darwin
  Trellis 1.14.0: February 16th, 2022
---------------------------------------------------
failed to validate
/home/joshb.linux/.ansible/tmp/ansible-
tmp-1686772911.0681658-91935-366201757888/source line 9: no argument after
keyword "AcceptEnv"
/home/joshb.linux/.ansible/tmp/ansible-
tmp-1686772911.0681658-91935-366201757888/source: terminating, 1 bad
configuration options
fatal: [default]: FAILED! => {"changed": false, "checksum": "ebb534a0a55caff91cde2c9129f07ad81c5e0c3a", "exit_status": 255, "stderr_lines": ["/home/joshb.linux/.ansible/tmp/ansible-tmp-1686772911.0681658-91935-366201757888/source line 9: no argument after keyword \"AcceptEnv\"", "/home/joshb.linux/.ansible/tmp/ansible-tmp-1686772911.0681658-91935-366201757888/source: terminating, 1 bad configuration options"], "stdout": "", "stdout_lines": []}

I will keep on digging!

8

I deleted all Lima instances and using the example project, I have run trellis up for Parallels and this is what I seeing going that route:

==> default: Booting VM...
There was an error while command execution. The command and stderr is shown below.

Command: ["/usr/local/bin/prlctl", "start", "c40969cc-4a46-450a-87a3-6186a798ce40"]

Stderr: Failed to start the VM: The virtual machine cannot be started due to a critical error. 

exit status 1

Not the most helpful error message :frowning:

Attempting to provision development:

➜ trellis provision development
Error while installing Ansible Galaxy roles:
ERROR: Ansible could not initialize the preferred locale: unsupported locale setting

This may be a temporary network issue. Please try again.
Running command => ansible-playbook dev.yml --inventory-file=/Users/joshb/_Development/_Trellis/examples/example.com/trellis/.trellis/lima/inventory -e env=development
ERROR: Ansible could not initialize the preferred locale: unsupported locale setting
exit status 1
9

Just realized I still had some Lima references in .trellis, so I destroyed everything and removed that folder and attempted another one with Parallels and here is what I get now:

==> default: Booting VM...
==> default: Unregistering the box VM image...
There was an error while command execution. The command and stderr is shown below.

Command: ["/usr/local/bin/prlctl", "start", "731cad0c-f41c-4588-bef3-a8170c9d88c8"]

Stderr: Failed to start the VM: The virtual machine cannot be started due to a critical error. 

exit status 1
10

I found some info on the Parallels forum that suggested a restart. That actually worked and got me thru the last error I posted about, however, it still starts with this error:

➜ trellis up
Error while installing Ansible Galaxy roles:
ERROR: Ansible could not initialize the preferred locale: unsupported locale setting

This may be a temporary network issue. Please try again.
Running command => vagrant up

Fails here now:

==> default: Installing the proper version of Parallels Tools. This may take a few minutes...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ptiagent-cmd --install

Stdout from the command:

ptiagent-cmd progress 3
ptiagent-cmd progress 15
Started installation of Parallels Guest Tools version '18.3.1.53614'
Hit:1 http://ports.ubuntu.com/ubuntu-ports jammy InRelease
Get:2 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease [119 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease [108 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease [110 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages [630 kB]
Get:6 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main Translation-en [184 kB]
Get:7 http://ports.ubuntu.com/ubuntu-ports jammy-updates/restricted arm64 Packages [188 kB]
Get:8 http://ports.ubuntu.com/ubuntu-ports jammy-updates/restricted Translation-en [52.8 kB]
Get:9 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe arm64 Packages [827 kB]
Get:10 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe Translation-en [196 kB]
Get:11 http://ports.ubuntu.com/ubuntu-ports jammy-updates/multiverse arm64 Packages [19.5 kB]
Get:12 http://ports.ubuntu.com/ubuntu-ports jammy-updates/multiverse Translation-en [8452 B]
Get:13 http://ports.ubuntu.com/ubuntu-ports jammy-backports/main arm64 Packages [40.6 kB]
Get:14 http://ports.ubuntu.com/ubuntu-ports jammy-backports/universe arm64 Packages [21.8 kB]
Get:15 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 Packages [413 kB]
Get:16 http://ports.ubuntu.com/ubuntu-ports jammy-security/main Translation-en [124 kB]
Get:17 http://ports.ubuntu.com/ubuntu-ports jammy-security/restricted arm64 Packages [187 kB]
Get:18 http://ports.ubuntu.com/ubuntu-ports jammy-security/restricted Translation-en [52.6 kB]
Get:19 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe arm64 Packages [642 kB]
Get:20 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe Translation-en [130 kB]
Get:21 http://ports.ubuntu.com/ubuntu-ports jammy-security/multiverse arm64 Packages [15.9 kB]
Get:22 http://ports.ubuntu.com/ubuntu-ports jammy-security/multiverse Translation-en [5828 B]
Fetched 4075 kB in 5s (842 kB/s)
Reading package lists...
Return code from apt-get update is 0
dpkg-preconfigure: unable to re-open stdin: No such file or directory
Selecting previously unselected package libxau6:arm64.
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 45533 files and directories currently installed.)
Preparing to unpack .../00-libxau6_1%3a1.0.9-1build5_arm64.deb ...
Unpacking libxau6:arm64 (1:1.0.9-1build5) ...
Selecting previously unselected package libxdmcp6:arm64.
Preparing to unpack .../01-libxdmcp6_1%3a1.1.3-0ubuntu5_arm64.deb ...
Unpacking libxdmcp6:arm64 (1:1.1.3-0ubuntu5) ...
Selecting previously unselected package libxcb1:arm64.
Preparing to unpack .../02-libxcb1_1.14-3ubuntu3_arm64.deb ...
Unpacking libxcb1:arm64 (1.14-3ubuntu3) ...
Selecting previously unselected package libx11-data.
Preparing to unpack .../03-libx11-data_2%3a1.7.5-1_all.deb ...
Unpacking libx11-data (2:1.7.5-1) ...
Selecting previously unselected package libx11-6:arm64.
Preparing to unpack .../04-libx11-6_2%3a1.7.5-1_arm64.deb ...
Unpacking libx11-6:arm64 (2:1.7.5-1) ...
Selecting previously unselected package gcc-11-base:arm64.
Preparing to unpack .../05-gcc-11-base_11.3.0-1ubuntu1~22.04.1_arm64.deb ...
Unpacking gcc-11-base:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Selecting previously unselected package libisl23:arm64.
Preparing to unpack .../06-libisl23_0.24-2build1_arm64.deb ...
Unpacking libisl23:arm64 (0.24-2build1) ...
Selecting previously unselected package libmpc3:arm64.
Preparing to unpack .../07-libmpc3_1.2.1-2build1_arm64.deb ...
Unpacking libmpc3:arm64 (1.2.1-2build1) ...
Selecting previously unselected package cpp-11.
Preparing to unpack .../08-cpp-11_11.3.0-1ubuntu1~22.04.1_arm64.deb ...
Unpacking cpp-11 (11.3.0-1ubuntu1~22.04.1) ...
Selecting previously unselected package cpp.
Preparing to unpack .../09-cpp_4%3a11.2.0-1ubuntu1_arm64.deb ...
Unpacking cpp (4:11.2.0-1ubuntu1) ...
Selecting previously unselected package fonts-dejavu-core.
Preparing to unpack .../10-fonts-dejavu-core_2.37-2build1_all.deb ...
Unpacking fonts-dejavu-core (2.37-2build1) ...
Selecting previously unselected package fontconfig-config.
Preparing to unpack .../11-fontconfig-config_2.13.1-4.2ubuntu5_all.deb ...
Unpacking fontconfig-config (2.13.1-4.2ubuntu5) ...
Selecting previously unselected package libcc1-0:arm64.
Preparing to unpack .../12-libcc1-0_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libcc1-0:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libgomp1:arm64.
Preparing to unpack .../13-libgomp1_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libgomp1:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libitm1:arm64.
Preparing to unpack .../14-libitm1_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libitm1:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libatomic1:arm64.
Preparing to unpack .../15-libatomic1_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libatomic1:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libasan6:arm64.
Preparing to unpack .../16-libasan6_11.3.0-1ubuntu1~22.04.1_arm64.deb ...
Unpacking libasan6:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Selecting previously unselected package liblsan0:arm64.
Preparing to unpack .../17-liblsan0_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking liblsan0:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libtsan0:arm64.
Preparing to unpack .../18-libtsan0_11.3.0-1ubuntu1~22.04.1_arm64.deb ...
Unpacking libtsan0:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Selecting previously unselected package libubsan1:arm64.
Preparing to unpack .../19-libubsan1_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libubsan1:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libhwasan0:arm64.
Preparing to unpack .../20-libhwasan0_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libhwasan0:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libgcc-11-dev:arm64.
Preparing to unpack .../21-libgcc-11-dev_11.3.0-1ubuntu1~22.04.1_arm64.deb ...
Unpacking libgcc-11-dev:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Selecting previously unselected package gcc-11.
Preparing to unpack .../22-gcc-11_11.3.0-1ubuntu1~22.04.1_arm64.deb ...
Unpacking gcc-11 (11.3.0-1ubuntu1~22.04.1) ...
Selecting previously unselected package gcc.
Preparing to unpack .../23-gcc_4%3a11.2.0-1ubuntu1_arm64.deb ...
Unpacking gcc (4:11.2.0-1ubuntu1) ...
Selecting previously unselected package libc-dev-bin.
Preparing to unpack .../24-libc-dev-bin_2.35-0ubuntu3.1_arm64.deb ...
Unpacking libc-dev-bin (2.35-0ubuntu3.1) ...
Selecting previously unselected package libfontconfig1:arm64.
Preparing to unpack .../25-libfontconfig1_2.13.1-4.2ubuntu5_arm64.deb ...
Unpacking libfontconfig1:arm64 (2.13.1-4.2ubuntu5) ...
Selecting previously unselected package libjpeg-turbo8:arm64.
Preparing to unpack .../26-libjpeg-turbo8_2.1.2-0ubuntu1_arm64.deb ...
Unpacking libjpeg-turbo8:arm64 (2.1.2-0ubuntu1) ...
Selecting previously unselected package libjpeg8:arm64.
Preparing to unpack .../27-libjpeg8_8c-2ubuntu10_arm64.deb ...
Unpacking libjpeg8:arm64 (8c-2ubuntu10) ...
Selecting previously unselected package libdeflate0:arm64.
Preparing to unpack .../28-libdeflate0_1.10-2_arm64.deb ...
Unpacking libdeflate0:arm64 (1.10-2) ...
Selecting previously unselected package libjbig0:arm64.
Preparing to unpack .../29-libjbig0_2.1-3.1ubuntu0.22.04.1_arm64.deb ...
Unpacking libjbig0:arm64 (2.1-3.1ubuntu0.22.04.1) ...
Selecting previously unselected package libwebp7:arm64.
Preparing to unpack .../30-libwebp7_1.2.2-2ubuntu0.22.04.1_arm64.deb ...
Unpacking libwebp7:arm64 (1.2.2-2ubuntu0.22.04.1) ...
Selecting previously unselected package libtiff5:arm64.
Preparing to unpack .../31-libtiff5_4.3.0-6ubuntu0.4_arm64.deb ...
Unpacking libtiff5:arm64 (4.3.0-6ubuntu0.4) ...
Selecting previously unselected package libxpm4:arm64.
Preparing to unpack .../32-libxpm4_1%3a3.5.12-1ubuntu0.22.04.1_arm64.deb ...
Unpacking libxpm4:arm64 (1:3.5.12-1ubuntu0.22.04.1) ...
Selecting previously unselected package libgd3:arm64.
Preparing to unpack .../33-libgd3_2.3.0-2ubuntu2_arm64.deb ...
Unpacking libgd3:arm64 (2.3.0-2ubuntu2) ...
Selecting previously unselected package libc-devtools.
Preparing to unpack .../34-libc-devtools_2.35-0ubuntu3.1_arm64.deb ...
Unpacking libc-devtools (2.35-0ubuntu3.1) ...
Selecting previously unselected package linux-libc-dev:arm64.
Preparing to unpack .../35-linux-libc-dev_5.15.0-73.80_arm64.deb ...
Unpacking linux-libc-dev:arm64 (5.15.0-73.80) ...
Selecting previously unselected package libcrypt-dev:arm64.
Preparing to unpack .../36-libcrypt-dev_1%3a4.4.27-1_arm64.deb ...
Unpacking libcrypt-dev:arm64 (1:4.4.27-1) ...
Selecting previously unselected package rpcsvc-proto.
Preparing to unpack .../37-rpcsvc-proto_1.4.2-0ubuntu6_arm64.deb ...
Unpacking rpcsvc-proto (1.4.2-0ubuntu6) ...
Selecting previously unselected package libtirpc-dev:arm64.
Preparing to unpack .../38-libtirpc-dev_1.3.2-2ubuntu0.1_arm64.deb ...
Unpacking libtirpc-dev:arm64 (1.3.2-2ubuntu0.1) ...
Selecting previously unselected package libnsl-dev:arm64.
Preparing to unpack .../39-libnsl-dev_1.3.0-2build2_arm64.deb ...
Unpacking libnsl-dev:arm64 (1.3.0-2build2) ...
Selecting previously unselected package libc6-dev:arm64.
Preparing to unpack .../40-libc6-dev_2.35-0ubuntu3.1_arm64.deb ...
Unpacking libc6-dev:arm64 (2.35-0ubuntu3.1) ...
Selecting previously unselected package manpages-dev.
Preparing to unpack .../41-manpages-dev_5.10-1ubuntu1_all.deb ...
Unpacking manpages-dev (5.10-1ubuntu1) ...
Setting up gcc-11-base:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Setting up manpages-dev (5.10-1ubuntu1) ...
Setting up libxau6:arm64 (1:1.0.9-1build5) ...
Setting up libxdmcp6:arm64 (1:1.1.3-0ubuntu5) ...
Setting up libxcb1:arm64 (1.14-3ubuntu3) ...
Setting up libdeflate0:arm64 (1.10-2) ...
Setting up linux-libc-dev:arm64 (5.15.0-73.80) ...
Setting up libgomp1:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up libjbig0:arm64 (2.1-3.1ubuntu0.22.04.1) ...
Setting up libasan6:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Setting up libtirpc-dev:arm64 (1.3.2-2ubuntu0.1) ...
Setting up rpcsvc-proto (1.4.2-0ubuntu6) ...
Setting up libx11-data (2:1.7.5-1) ...
Setting up libmpc3:arm64 (1.2.1-2build1) ...
Setting up libatomic1:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up fonts-dejavu-core (2.37-2build1) ...
Setting up libjpeg-turbo8:arm64 (2.1.2-0ubuntu1) ...
Setting up libwebp7:arm64 (1.2.2-2ubuntu0.22.04.1) ...
Setting up libubsan1:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up libnsl-dev:arm64 (1.3.0-2build2) ...
Setting up libhwasan0:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up libcrypt-dev:arm64 (1:4.4.27-1) ...
Setting up libx11-6:arm64 (2:1.7.5-1) ...
Setting up libisl23:arm64 (0.24-2build1) ...
Setting up libc-dev-bin (2.35-0ubuntu3.1) ...
Setting up libcc1-0:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up liblsan0:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up libitm1:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up libtsan0:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Setting up libjpeg8:arm64 (8c-2ubuntu10) ...
Setting up cpp-11 (11.3.0-1ubuntu1~22.04.1) ...
Setting up libxpm4:arm64 (1:3.5.12-1ubuntu0.22.04.1) ...
Setting up fontconfig-config (2.13.1-4.2ubuntu5) ...
Setting up libgcc-11-dev:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Setting up gcc-11 (11.3.0-1ubuntu1~22.04.1) ...
Setting up cpp (4:11.2.0-1ubuntu1) ...
Setting up libc6-dev:arm64 (2.35-0ubuntu3.1) ...
Setting up libtiff5:arm64 (4.3.0-6ubuntu0.4) ...
Setting up libfontconfig1:arm64 (2.13.1-4.2ubuntu5) ...
Setting up gcc (4:11.2.0-1ubuntu1) ...
Setting up libgd3:arm64 (2.3.0-2ubuntu2) ...
Setting up libc-devtools (2.35-0ubuntu3.1) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...

Running kernel seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.
E: Package 'linux-headers-5.15.0-71-generic' has no installation candidate
m linux-headers-5.15.0-71-generic
o dkms
o libelf-dev
Error: failed to install mandatory packages.
Error: failed to install or upgrade Parallels Guest Tools!


Stderr from the command:


exit status 1
11

Looks like same as Package 'linux-headers-5.15.0-67-generic' has no installation candidate m linux-headers-5.15.0-67-generic - #3 by MWDelaney

Try doing what @MWDelaney suggests and downgrading the box to 20.04

12

Tried to destroy the box and try with the downgraded version but get this message. Will need to come back to this tomorrow, gotta run for today…

➜ vagrant destroy 5ec9cfd
/Users/joshb/.vagrant.d/gems/3.1.4/gems/vagrant-parallels-2.4.0/lib/vagrant-parallels/util/common.rb:9:in `is_macvm': undefined method `directory' for nil:NilClass (NoMethodError)

          return !!Dir.glob(machine.box.directory.join('*.macvm')).first
                                       ^^^^^^^^^^
        from /Users/joshb/.vagrant.d/gems/3.1.4/gems/vagrant-parallels-2.4.0/lib/vagrant-parallels/synced_folder.rb:10:in `usable?'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builtin/mixin_synced_folders.rb:41:in `block in default_synced_folder_type'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builtin/mixin_synced_folders.rb:40:in `each'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builtin/mixin_synced_folders.rb:40:in `default_synced_folder_type'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builtin/mixin_synced_folders.rb:170:in `synced_folders'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/machine.rb:633:in `synced_folders'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/plugins/kernel_v2/config/vm.rb:745:in `validate'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/config/v2/root.rb:72:in `block in validate'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/config/v2/root.rb:67:in `each'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/config/v2/root.rb:67:in `validate'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builtin/config_validate.rb:15:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/warden.rb:48:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builder.rb:180:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/runner.rb:101:in `block in run'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/util/busy.rb:19:in `busy'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/runner.rb:101:in `run'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/machine.rb:248:in `action_raw'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/machine.rb:217:in `block in action'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/environment.rb:631:in `lock'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/machine.rb:203:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/machine.rb:203:in `action'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/batch_action.rb:86:in `block (2 levels) in run'
13

OK, back at it. Trying to sort things out here one step at a time.
So upon creating a new trellis project again today, this is the first thing that happens:

➜ trellis up
Error while installing Ansible Galaxy roles:
ERROR: Ansible could not initialize the preferred locale: unsupported locale setting

This may be a temporary network issue. Please try again.
Running command => vagrant up

I attempted to trellis up anyhow and it stops here:


The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o vers=3 10.211.55.2:/Users/joshb/_Development/_Trellis/examples/testing.com/site /vagrant-nfs-testing.com

Stdout from the command:



Stderr from the command:

mount.nfs: requested NFS version or transport protocol is not supported

exit status 1

Keepin on digging… but dang, I was hoping for a smoother setup with a brand new macbook…

14

Is your hard drive/folder with the project encrypted? If you’re using FileVault or whatever then you’re not going to be able to get up and running

From https://roots.io/trellis/docs/local-development/#vagrant: https://developer.hashicorp.com/vagrant/docs/synced-folders/nfs#other-notes

15

I am adding new information here as come across it / fix things for future users who may run into this. I found the fix that was causing most of the headache.

I just completely reformatted the new m2 macbook to start from scratch, starting with nothing but getting Trellis up and running.

I’ve been running into this error since I bought this machine earlier this week and while running ansible commands, this is what pooped out all the time:

_Development/_Trellis/testing ➜ ansible ERROR: Ansible could not initialize the preferred locale: unsupported locale setting

It was not easy to discover how to get past this but ultimately, the fix was to reset the locale by running the following command. I have no idea what this does but it updated all the utf enoding and allows ansible commands to be performed.

LC_ALL=en_US.utf-8

Development/_Trellis/testing 
➜ locale
LANG="en_US.UTF-8"
LC_COLLATE="en_US.utf-8"
LC_CTYPE="en_US.utf-8"
LC_MESSAGES="en_US.utf-8"
LC_MONETARY="en_US.utf-8"
LC_NUMERIC="en_US.utf-8"
LC_TIME="en_US.utf-8"
LC_ALL="en_US.utf-8"

and was finally able to run an ansible command to fetch the version details:

_Development/_Trellis/testing 
➜ ansible --version
ansible [core 2.15.0]
  config file = None
  configured module search path = ['/Users/joshb/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /opt/homebrew/Cellar/ansible/8.0.0/libexec/lib/python3.11/site-packages/ansible
  ansible collection location = /Users/joshb/.ansible/collections:/usr/share/ansible/collections
  executable location = /opt/homebrew/bin/ansible
  python version = 3.11.4 (main, Jun  7 2023, 00:34:59) [Clang 14.0.3 (clang-1403.0.22.14.1)] (/opt/homebrew/Cellar/ansible/8.0.0/libexec/bin/python3.11)
  jinja version = 3.1.2
  libyaml = True

Then I attempted to trellis up a new example test and almost punched myself before remembering I need to install the vagrant plugin: vagrant plugin install vagrant-parallels

Finally, I ran trellis up again and running into a new issue:

==> default: Installing the proper version of Parallels Tools. This may take a few minutes...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ptiagent-cmd --install

Stdout from the command:

ptiagent-cmd progress 3
ptiagent-cmd progress 15
Started installation of Parallels Guest Tools version '18.3.1.53614'
Hit:1 http://ports.ubuntu.com/ubuntu-ports jammy InRelease
Get:2 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease [119 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease [108 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease [110 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages [631 kB]
Get:6 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main Translation-en [185 kB]
Get:7 http://ports.ubuntu.com/ubuntu-ports jammy-updates/restricted arm64 Packages [188 kB]
Get:8 http://ports.ubuntu.com/ubuntu-ports jammy-updates/restricted Translation-en [52.8 kB]
Get:9 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe arm64 Packages [828 kB]
Get:10 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe Translation-en [197 kB]
Get:11 http://ports.ubuntu.com/ubuntu-ports jammy-updates/multiverse arm64 Packages [19.5 kB]
Get:12 http://ports.ubuntu.com/ubuntu-ports jammy-updates/multiverse Translation-en [8452 B]
Get:13 http://ports.ubuntu.com/ubuntu-ports jammy-backports/main arm64 Packages [40.6 kB]
Get:14 http://ports.ubuntu.com/ubuntu-ports jammy-backports/universe arm64 Packages [21.8 kB]
Get:15 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 Packages [415 kB]
Get:16 http://ports.ubuntu.com/ubuntu-ports jammy-security/main Translation-en [124 kB]
Get:17 http://ports.ubuntu.com/ubuntu-ports jammy-security/restricted arm64 Packages [187 kB]
Get:18 http://ports.ubuntu.com/ubuntu-ports jammy-security/restricted Translation-en [52.6 kB]
Get:19 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe arm64 Packages [642 kB]
Get:20 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe Translation-en [130 kB]
Get:21 http://ports.ubuntu.com/ubuntu-ports jammy-security/multiverse arm64 Packages [15.9 kB]
Get:22 http://ports.ubuntu.com/ubuntu-ports jammy-security/multiverse Translation-en [5828 B]
Fetched 4080 kB in 5s (756 kB/s)
Reading package lists...
Return code from apt-get update is 0
dpkg-preconfigure: unable to re-open stdin: No such file or directory
Selecting previously unselected package libxau6:arm64.
(Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 45533 files and directories currently installed.)
Preparing to unpack .../00-libxau6_1%3a1.0.9-1build5_arm64.deb ...
Unpacking libxau6:arm64 (1:1.0.9-1build5) ...
Selecting previously unselected package libxdmcp6:arm64.
Preparing to unpack .../01-libxdmcp6_1%3a1.1.3-0ubuntu5_arm64.deb ...
Unpacking libxdmcp6:arm64 (1:1.1.3-0ubuntu5) ...
Selecting previously unselected package libxcb1:arm64.
Preparing to unpack .../02-libxcb1_1.14-3ubuntu3_arm64.deb ...
Unpacking libxcb1:arm64 (1.14-3ubuntu3) ...
Selecting previously unselected package libx11-data.
Preparing to unpack .../03-libx11-data_2%3a1.7.5-1ubuntu0.2_all.deb ...
Unpacking libx11-data (2:1.7.5-1ubuntu0.2) ...
Selecting previously unselected package libx11-6:arm64.
Preparing to unpack .../04-libx11-6_2%3a1.7.5-1ubuntu0.2_arm64.deb ...
Unpacking libx11-6:arm64 (2:1.7.5-1ubuntu0.2) ...
Selecting previously unselected package gcc-11-base:arm64.
Preparing to unpack .../05-gcc-11-base_11.3.0-1ubuntu1~22.04.1_arm64.deb ...
Unpacking gcc-11-base:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Selecting previously unselected package libisl23:arm64.
Preparing to unpack .../06-libisl23_0.24-2build1_arm64.deb ...
Unpacking libisl23:arm64 (0.24-2build1) ...
Selecting previously unselected package libmpc3:arm64.
Preparing to unpack .../07-libmpc3_1.2.1-2build1_arm64.deb ...
Unpacking libmpc3:arm64 (1.2.1-2build1) ...
Selecting previously unselected package cpp-11.
Preparing to unpack .../08-cpp-11_11.3.0-1ubuntu1~22.04.1_arm64.deb ...
Unpacking cpp-11 (11.3.0-1ubuntu1~22.04.1) ...
Selecting previously unselected package cpp.
Preparing to unpack .../09-cpp_4%3a11.2.0-1ubuntu1_arm64.deb ...
Unpacking cpp (4:11.2.0-1ubuntu1) ...
Selecting previously unselected package fonts-dejavu-core.
Preparing to unpack .../10-fonts-dejavu-core_2.37-2build1_all.deb ...
Unpacking fonts-dejavu-core (2.37-2build1) ...
Selecting previously unselected package fontconfig-config.
Preparing to unpack .../11-fontconfig-config_2.13.1-4.2ubuntu5_all.deb ...
Unpacking fontconfig-config (2.13.1-4.2ubuntu5) ...
Selecting previously unselected package libcc1-0:arm64.
Preparing to unpack .../12-libcc1-0_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libcc1-0:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libgomp1:arm64.
Preparing to unpack .../13-libgomp1_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libgomp1:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libitm1:arm64.
Preparing to unpack .../14-libitm1_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libitm1:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libatomic1:arm64.
Preparing to unpack .../15-libatomic1_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libatomic1:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libasan6:arm64.
Preparing to unpack .../16-libasan6_11.3.0-1ubuntu1~22.04.1_arm64.deb ...
Unpacking libasan6:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Selecting previously unselected package liblsan0:arm64.
Preparing to unpack .../17-liblsan0_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking liblsan0:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libtsan0:arm64.
Preparing to unpack .../18-libtsan0_11.3.0-1ubuntu1~22.04.1_arm64.deb ...
Unpacking libtsan0:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Selecting previously unselected package libubsan1:arm64.
Preparing to unpack .../19-libubsan1_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libubsan1:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libhwasan0:arm64.
Preparing to unpack .../20-libhwasan0_12.1.0-2ubuntu1~22.04_arm64.deb ...
Unpacking libhwasan0:arm64 (12.1.0-2ubuntu1~22.04) ...
Selecting previously unselected package libgcc-11-dev:arm64.
Preparing to unpack .../21-libgcc-11-dev_11.3.0-1ubuntu1~22.04.1_arm64.deb ...
Unpacking libgcc-11-dev:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Selecting previously unselected package gcc-11.
Preparing to unpack .../22-gcc-11_11.3.0-1ubuntu1~22.04.1_arm64.deb ...
Unpacking gcc-11 (11.3.0-1ubuntu1~22.04.1) ...
Selecting previously unselected package gcc.
Preparing to unpack .../23-gcc_4%3a11.2.0-1ubuntu1_arm64.deb ...
Unpacking gcc (4:11.2.0-1ubuntu1) ...
Selecting previously unselected package libc-dev-bin.
Preparing to unpack .../24-libc-dev-bin_2.35-0ubuntu3.1_arm64.deb ...
Unpacking libc-dev-bin (2.35-0ubuntu3.1) ...
Selecting previously unselected package libfontconfig1:arm64.
Preparing to unpack .../25-libfontconfig1_2.13.1-4.2ubuntu5_arm64.deb ...
Unpacking libfontconfig1:arm64 (2.13.1-4.2ubuntu5) ...
Selecting previously unselected package libjpeg-turbo8:arm64.
Preparing to unpack .../26-libjpeg-turbo8_2.1.2-0ubuntu1_arm64.deb ...
Unpacking libjpeg-turbo8:arm64 (2.1.2-0ubuntu1) ...
Selecting previously unselected package libjpeg8:arm64.
Preparing to unpack .../27-libjpeg8_8c-2ubuntu10_arm64.deb ...
Unpacking libjpeg8:arm64 (8c-2ubuntu10) ...
Selecting previously unselected package libdeflate0:arm64.
Preparing to unpack .../28-libdeflate0_1.10-2_arm64.deb ...
Unpacking libdeflate0:arm64 (1.10-2) ...
Selecting previously unselected package libjbig0:arm64.
Preparing to unpack .../29-libjbig0_2.1-3.1ubuntu0.22.04.1_arm64.deb ...
Unpacking libjbig0:arm64 (2.1-3.1ubuntu0.22.04.1) ...
Selecting previously unselected package libwebp7:arm64.
Preparing to unpack .../30-libwebp7_1.2.2-2ubuntu0.22.04.1_arm64.deb ...
Unpacking libwebp7:arm64 (1.2.2-2ubuntu0.22.04.1) ...
Selecting previously unselected package libtiff5:arm64.
Preparing to unpack .../31-libtiff5_4.3.0-6ubuntu0.4_arm64.deb ...
Unpacking libtiff5:arm64 (4.3.0-6ubuntu0.4) ...
Selecting previously unselected package libxpm4:arm64.
Preparing to unpack .../32-libxpm4_1%3a3.5.12-1ubuntu0.22.04.1_arm64.deb ...
Unpacking libxpm4:arm64 (1:3.5.12-1ubuntu0.22.04.1) ...
Selecting previously unselected package libgd3:arm64.
Preparing to unpack .../33-libgd3_2.3.0-2ubuntu2_arm64.deb ...
Unpacking libgd3:arm64 (2.3.0-2ubuntu2) ...
Selecting previously unselected package libc-devtools.
Preparing to unpack .../34-libc-devtools_2.35-0ubuntu3.1_arm64.deb ...
Unpacking libc-devtools (2.35-0ubuntu3.1) ...
Selecting previously unselected package linux-libc-dev:arm64.
Preparing to unpack .../35-linux-libc-dev_5.15.0-73.80_arm64.deb ...
Unpacking linux-libc-dev:arm64 (5.15.0-73.80) ...
Selecting previously unselected package libcrypt-dev:arm64.
Preparing to unpack .../36-libcrypt-dev_1%3a4.4.27-1_arm64.deb ...
Unpacking libcrypt-dev:arm64 (1:4.4.27-1) ...
Selecting previously unselected package rpcsvc-proto.
Preparing to unpack .../37-rpcsvc-proto_1.4.2-0ubuntu6_arm64.deb ...
Unpacking rpcsvc-proto (1.4.2-0ubuntu6) ...
Selecting previously unselected package libtirpc-dev:arm64.
Preparing to unpack .../38-libtirpc-dev_1.3.2-2ubuntu0.1_arm64.deb ...
Unpacking libtirpc-dev:arm64 (1.3.2-2ubuntu0.1) ...
Selecting previously unselected package libnsl-dev:arm64.
Preparing to unpack .../39-libnsl-dev_1.3.0-2build2_arm64.deb ...
Unpacking libnsl-dev:arm64 (1.3.0-2build2) ...
Selecting previously unselected package libc6-dev:arm64.
Preparing to unpack .../40-libc6-dev_2.35-0ubuntu3.1_arm64.deb ...
Unpacking libc6-dev:arm64 (2.35-0ubuntu3.1) ...
Selecting previously unselected package manpages-dev.
Preparing to unpack .../41-manpages-dev_5.10-1ubuntu1_all.deb ...
Unpacking manpages-dev (5.10-1ubuntu1) ...
Setting up gcc-11-base:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Setting up manpages-dev (5.10-1ubuntu1) ...
Setting up libxau6:arm64 (1:1.0.9-1build5) ...
Setting up libxdmcp6:arm64 (1:1.1.3-0ubuntu5) ...
Setting up libxcb1:arm64 (1.14-3ubuntu3) ...
Setting up libdeflate0:arm64 (1.10-2) ...
Setting up linux-libc-dev:arm64 (5.15.0-73.80) ...
Setting up libgomp1:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up libjbig0:arm64 (2.1-3.1ubuntu0.22.04.1) ...
Setting up libasan6:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Setting up libtirpc-dev:arm64 (1.3.2-2ubuntu0.1) ...
Setting up rpcsvc-proto (1.4.2-0ubuntu6) ...
Setting up libx11-data (2:1.7.5-1ubuntu0.2) ...
Setting up libmpc3:arm64 (1.2.1-2build1) ...
Setting up libatomic1:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up fonts-dejavu-core (2.37-2build1) ...
Setting up libjpeg-turbo8:arm64 (2.1.2-0ubuntu1) ...
Setting up libwebp7:arm64 (1.2.2-2ubuntu0.22.04.1) ...
Setting up libubsan1:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up libnsl-dev:arm64 (1.3.0-2build2) ...
Setting up libhwasan0:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up libcrypt-dev:arm64 (1:4.4.27-1) ...
Setting up libx11-6:arm64 (2:1.7.5-1ubuntu0.2) ...
Setting up libisl23:arm64 (0.24-2build1) ...
Setting up libc-dev-bin (2.35-0ubuntu3.1) ...
Setting up libcc1-0:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up liblsan0:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up libitm1:arm64 (12.1.0-2ubuntu1~22.04) ...
Setting up libtsan0:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Setting up libjpeg8:arm64 (8c-2ubuntu10) ...
Setting up cpp-11 (11.3.0-1ubuntu1~22.04.1) ...
Setting up libxpm4:arm64 (1:3.5.12-1ubuntu0.22.04.1) ...
Setting up fontconfig-config (2.13.1-4.2ubuntu5) ...
Setting up libgcc-11-dev:arm64 (11.3.0-1ubuntu1~22.04.1) ...
Setting up gcc-11 (11.3.0-1ubuntu1~22.04.1) ...
Setting up cpp (4:11.2.0-1ubuntu1) ...
Setting up libc6-dev:arm64 (2.35-0ubuntu3.1) ...
Setting up libtiff5:arm64 (4.3.0-6ubuntu0.4) ...
Setting up libfontconfig1:arm64 (2.13.1-4.2ubuntu5) ...
Setting up gcc (4:11.2.0-1ubuntu1) ...
Setting up libgd3:arm64 (2.3.0-2ubuntu2) ...
Setting up libc-devtools (2.35-0ubuntu3.1) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...

Running kernel seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.
E: Package 'linux-headers-5.15.0-71-generic' has no installation candidate
m linux-headers-5.15.0-71-generic
o dkms
o libelf-dev
Error: failed to install mandatory packages.
Error: failed to install or upgrade Parallels Guest Tools!


Stderr from the command:


exit status 1

I decided to destroy the box and start over again by downgrading Ubuntu to 20.04 from 22.04 but was unable to destroy. It gives me this attempting to do so:

➜ vagrant destroy 5ec9cfd
/Users/joshb/.vagrant.d/gems/3.1.4/gems/vagrant-parallels-2.4.0/lib/vagrant-parallels/util/common.rb:9:in `is_macvm': undefined method `directory' for nil:NilClass (NoMethodError)

          return !!Dir.glob(machine.box.directory.join('*.macvm')).first
                                       ^^^^^^^^^^
        from /Users/joshb/.vagrant.d/gems/3.1.4/gems/vagrant-parallels-2.4.0/lib/vagrant-parallels/synced_folder.rb:10:in `usable?'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builtin/mixin_synced_folders.rb:41:in `block in default_synced_folder_type'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builtin/mixin_synced_folders.rb:40:in `each'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builtin/mixin_synced_folders.rb:40:in `default_synced_folder_type'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builtin/mixin_synced_folders.rb:170:in `synced_folders'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/machine.rb:633:in `synced_folders'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/plugins/kernel_v2/config/vm.rb:745:in `validate'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/config/v2/root.rb:72:in `block in validate'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/config/v2/root.rb:67:in `each'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/config/v2/root.rb:67:in `validate'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builtin/config_validate.rb:15:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/warden.rb:48:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/builder.rb:180:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/runner.rb:101:in `block in run'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/util/busy.rb:19:in `busy'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/action/runner.rb:101:in `run'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/machine.rb:248:in `action_raw'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/machine.rb:217:in `block in action'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/environment.rb:631:in `lock'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/machine.rb:203:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/machine.rb:203:in `action'
        from /opt/vagrant/embedded/gems/gems/vagrant-2.3.6/lib/vagrant/batch_action.rb:86:in `block (2 levels) in run'

Instead, I stopped the machine thru Parallels and removed it, then pruned the vagrant list and it was gone.

Next, I cloned down a new trellis project to try again but was met with this straight away, back to the locale bs:

_Development/_Trellis/testing 
➜ trellis new testing2.com
Creating new Trellis project in /Users/joshb/_Development/_Trellis/testing/testing2.com

Site domain [testing2.com]: 

✔ testing2.com
Initializing project...

[✓] Created virtualenv (/Users/joshb/_Development/_Trellis/testing/testing2.com/trellis/.trellis/virtualenv)
[✓] Ensure pip is up to date
[✓] Dependencies installed
Error while installing Ansible Galaxy roles:
ERROR: Ansible could not initialize the preferred locale: unsupported locale setting

This may be a temporary network issue. Please try again.

_Development/_Trellis/testing took 24.0s 
➜

Checking locale, its back to this:

➜ locale
LANG="en_US.UTF-8"
LC_COLLATE="C"
LC_CTYPE="C"
LC_MESSAGES="C"
LC_MONETARY="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_ALL="C"

I removed the testing2.com project, reset the locale again and cloned a new trellis project down known as testing3.com and I starting to get somewhere:

_Development/_Trellis/testing 
➜ trellis new testing3.com
Creating new Trellis project in /Users/joshb/_Development/_Trellis/testing/testing3.com

Site domain [testing3.com]: 

✔ testing3.com
Initializing project...

[✓] Created virtualenv (/Users/joshb/_Development/_Trellis/testing/testing3.com/trellis/.trellis/virtualenv)
[✓] Ensure pip is up to date
[✓] Dependencies installed
Starting galaxy role install process
- downloading role 'composer', owned by geerlingguy
- downloading role from https://github.com/geerlingguy/ansible-role-composer/archive/1.9.0.tar.gz
- extracting composer to /Users/joshb/_Development/_Trellis/testing/testing3.com/trellis/vendor/roles/composer
- composer (1.9.0) was installed successfully
- downloading role 'ntp', owned by geerlingguy
- downloading role from https://github.com/geerlingguy/ansible-role-ntp/archive/2.3.1.tar.gz
- extracting ntp to /Users/joshb/_Development/_Trellis/testing/testing3.com/trellis/vendor/roles/ntp
- ntp (2.3.1) was installed successfully
- downloading role 'logrotate', owned by nickhammond
- downloading role from https://github.com/nickhammond/ansible-logrotate/archive/v0.0.5.tar.gz
- extracting logrotate to /Users/joshb/_Development/_Trellis/testing/testing3.com/trellis/vendor/roles/logrotate
- logrotate (v0.0.5) was installed successfully
- downloading role 'swapfile', owned by oefenweb
- downloading role from https://github.com/Oefenweb/ansible-swapfile/archive/v2.0.36.tar.gz
- extracting swapfile to /Users/joshb/_Development/_Trellis/testing/testing3.com/trellis/vendor/roles/swapfile
- swapfile (v2.0.36) was installed successfully
- downloading role 'mailpit', owned by roots
- downloading role from https://github.com/roots/ansible-role-mailpit/archive/v1.0.0.tar.gz
- extracting mailpit to /Users/joshb/_Development/_Trellis/testing/testing3.com/trellis/vendor/roles/mailpit
- mailpit (v1.0.0) was installed successfully


testing3.com project created with versions:
  Trellis v1.21.0
  Bedrock v1.22.2

_Development/_Trellis/testing took 29.0s 
➜

Alright, now onto trellis up.
Whoops! Forgot to change the Ubuntu version on testing3.com before starting it up and was met with the error from above. Destroyed the box successfully this time from command prompt and ran again…

Now I am finally up and running with Parallels.

So I checked locale again and it has been reset:

_Trellis/testing/testing3.com 
➜ locale      
LANG="en_US.UTF-8"
LC_COLLATE="C"
LC_CTYPE="C"
LC_MESSAGES="C"
LC_MONETARY="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_ALL="C"

_Trellis/testing/testing3.com 
➜

Now I ran another install of Trellis, worked fine and checked locale again and its back to where it should be:

_Trellis/testing/testing4.com 
➜ locale
LANG="en_US.UTF-8"
LC_COLLATE="en_US.utf-8"
LC_CTYPE="en_US.utf-8"
LC_MESSAGES="en_US.utf-8"
LC_MONETARY="en_US.utf-8"
LC_NUMERIC="en_US.utf-8"
LC_TIME="en_US.utf-8"
LC_ALL="en_US.utf-8"

_Trellis/testing/testing4.com 
➜

Not sure what the deal is with the locale stuff but that seems to have been the entire problem. That AND reverting back to Ubunutu. 20.04 vs 22.04

16

So, I have testing3.com running on Parallels fine
AND I have testing4.com running on Lima just fine!
Yay.
Mindblown: a blog about getting trellis running on a new macbook m2

Now begins the next headache :joy: to get some existing projects up and running…

However, checking locale again, shows the lines reverted back.
Does anyone know anything this and what the deal is?

testing/testing4.com/site via 🐘 v8.2.7 
➜ locale
LANG="en_US.UTF-8"
LC_COLLATE="C"
LC_CTYPE="C"
LC_MESSAGES="C"
LC_MONETARY="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_ALL="C"
17

Furthermore: I was able to get an existing project running on Parallels using the updates to the 3 Trellis files that @ben mentioned earlier in this thread. Sucessfully ran the sync script and I am now running full speed ahead. So that’s awesome.

AND wow, the latest Roots stack setup is so blazing fast and very nice to work with. Mad respect to those involved all these years.

Lastly, although I was able to get a couple of new test instances booted with Lima, I am running into the following error attempting to boot up the existing (year+ old) project. Happy it works with Parallels but wondering what this error may mean

TASK [sshd : Create a secure sshd_config] **************************************
System info:
  Ansible 2.12.10; Darwin
  Trellis 1.14.0: February 16th, 2022
---------------------------------------------------
failed to validate
/home/joshb.linux/.ansible/tmp/ansible-
tmp-1686876968.6534138-17804-151130621935976/source line 9: no argument after
keyword "AcceptEnv"
/home/joshb.linux/.ansible/tmp/ansible-
tmp-1686876968.6534138-17804-151130621935976/source: terminating, 1 bad
configuration options
fatal: [default]: FAILED! => {"changed": false, "checksum": "ebb534a0a55caff91cde2c9129f07ad81c5e0c3a", "exit_status": 255, "stderr_lines": ["/home/joshb.linux/.ansible/tmp/ansible-tmp-1686876968.6534138-17804-151130621935976/source line 9: no argument after keyword \"AcceptEnv\"", "/home/joshb.linux/.ansible/tmp/ansible-tmp-1686876968.6534138-17804-151130621935976/source: terminating, 1 bad configuration options"], "stdout": "", "stdout_lines": []}
1 Like
18

I asked my good friend ChatGPT about this and here is the result: Locale Fix for MacBook

Curious if it does actually help. I’ve become best friends with GPT recently ha. I don’t have any prior experience with this issue so was a genuine route to try find out the solution I feel.

19

That is umm… pretty amazing!

20

Onto another existing project and trying to get it up and running here on development and am running into this error which I’ve never encountered but found the fix, so here it is for anyone who stumbles on this.

TASK [mariadb : Install MySQL client] ******************************************
System info:
  Ansible 2.10.17; Vagrant 2.3.6; Darwin
  Trellis 1.8.0: February 12th, 2021
---------------------------------------------------
'/usr/bin/apt-get -y -o "Dpkg::Options::=--force-confdef" -o
"Dpkg::Options::=--force-confold"      install 'mariadb-client'' failed: E:
Unable to correct problems, you have held broken packages.

E: Unable to correct problems, you have held broken packages.
fatal: [default]: FAILED! => {"cache_update_time": 1655150587, "cache_updated": false, "changed": false, "rc": 100, "stderr_lines": ["E: Unable to correct problems, you have held broken packages."], "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\nSome packages could not be installed. This may mean that you have\nrequested an impossible situation or if you are using the unstable\ndistribution that some required packages have not yet been created\nor been moved out of Incoming.\nThe following information may help to resolve the situation:\n\nThe following packages have unmet dependencies:\n mariadb-client : Depends: mariadb-client-10.5 (>= 1:10.5.21+maria~ubu2004) but it is not installable\n", "stdout_lines": ["Reading package lists...", "Building dependency tree...", "Reading state information...", "Some packages could not be installed. This may mean that you have", "requested an impossible situation or if you are using the unstable", "distribution that some required packages have not yet been created", "or been moved out of Incoming.", "The following information may help to resolve the situation:", "", "The following packages have unmet dependencies:", " mariadb-client : Depends: mariadb-client-10.5 (>= 1:10.5.21+maria~ubu2004) but it is not installable"]}

This is what helped me get past this issue.

The first existing project I got up and running doesn’t reference architecture at all, so apparently it can be removed all together.

mariadb_ppa: "deb [arch=arm64] http://nyc2.mirrors.digitalocean.com/mariadb/repo/10.5/ubuntu {{ ansible_distribution_release }} main"

to this:

mariadb_ppa: "deb http://mirrors.gigenet.com/mariadb/repo/10.5/ubuntu {{ ansible_distribution_release }} main"

2 Likes