Open loicsaintroch opened 2 years ago
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.
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.
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.
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.
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?
What OS are you using?
macOS
What architecture are you using?
arm64
What Vagrant provider are you using?
parallels
Unexpected behavior
When using Parallels Desktop, Consul clients can connect to Consul servers but a connection error occurs. This prevents both Consul and Nomad client services to be registered in Consul even though they run as expected.
What kind of specifics do we need to set in Parallels Desktop to make this work as expected? This doesn't happen when using VirtualBox.
Related issues:
Steps to reproduce
Run HashiBox with Parallels Desktop.
Expected behavior
No connection errors. Both Consul and Nomad client services should be registered in Consul.
Logs