Parallels: Consul clients encounter connection error about hashibox HOT 5 OPEN

Indeed, you're right.

Edit: Upgrading Ubuntu to 22.04 won't fix the compatibility issues between amd64 and arm64. I'll try to find some time to investigate this Parallels issue and let you know.

from hashibox.

Hi @loicsaintroch,
could you please provide guidance on how to run it on VirtualBox on ARM64 as a temporary alternative. I've tried both vmvare and virtualbox, but none worked for me.

from hashibox.

Sure.

First, you need to reset the config files since we write the Consul HTTP token statically in two places:

$ git reset --hard

Also, I would make sure to destroy existing resources:

$ make destroy

Cleanup and set proper environment variables. Here's the .env I'd use for a fresh install given your setup:

export VAGRANT_CLIENT_RAM=2048
export VAGRANT_SERVER_RAM=1024
export VAGRANT_PROVIDER=virtualbox
export UBUNTU_VERSION=20.04-arm64

Run the init process:

$ make init

As far as I can see, the only thing that could potentially not work on Linux are these lines because sed doesn't have the exact same behavior between macOS and Linux iirc.

from hashibox.

Based on what I've tried, it should error because the box https://app.vagrantup.com/bento/boxes/ubuntu-20.04-arm64 is built only for parallels.

from hashibox.

PR opened. Everything seems to work as expected on Parallels Desktop now.
Can I let you try @makp0 and confirm it works for you as well?

from hashibox.