servian / hashiqube Goto Github PK

Hi there,

Please find in below image.

Description
Failed to create container configuration for image "fabiolb/fabio" ("sha256:3d652f62fddf53dba25b86b7d2ca7d472abb90dc0f195c0a95758ef540467b42"): volumes are not enabled; cannot mount host paths: "/vagrant/hashicorp/nomad/jobs:/etc/fabio"

For my workaround
On the fabio.nomad I'm comment the volumes.

The shell executing the quoted commands is Dash, and the string comparison [ $i == systemd-tmpfiles-setup.service ] is not POSIX-compliant, causing that loop to throw several errors and the deletion of files other than systemd-tmpfiles-setup.service to fail. Dash is very particular about POSIX.

Not sure whether it's this or something else that makes the consul service fail (there are many errors in the output and I'm still chasing them down), but at least this one is an easy fix: [ "$i" = "systemd-tmpfiles-setup.service" ]

What's not an easy fix is checking all the other shell code for similar mistakes.

Edit: The deletion is of files other than the matched string, obviously, but I forgot to invert the English logic...

When installing dbt with all default options using the command vagrant up --provision-with basetools,docsify,docker,postgresql,dbt, I received the error "hashiqube0.service.consul: ModuleNotFoundError: No module named 'pytz'".

I have found the fix and raised a PR here: #26

Hi,

would you consider exposing the Waypoint API(TCP9701) as well?
config.vm.network "forwarded_port", guest: 9701, host: 9701 # waypoint-api-nomad

Thanks,

Hello,
giving hashiqube a spin, I get the following error:

hashiqube0.service.consul: Error: Error creating S3 bucket: RequestError: send request failed
hashiqube0.service.consul: caused by: Put http://localhost:4572/localstack-s3-bucket: dial tcp 127.0.0.1:4572: connect: connection refused
hashiqube0.service.consul: 
hashiqube0.service.consul:   on main.tf line 37, in resource "aws_s3_bucket" "localstack-s3-bucket":
hashiqube0.service.consul:   37: resource "aws_s3_bucket" "localstack-s3-bucket" {
hashiqube0.service.consul: 
hashiqube0.service.consul: 
hashiqube0.service.consul: ++++ awslocal s3 ls..
hashiqube0.service.consul: 
hashiqube0.service.consul: Could not connect to the endpoint URL: "http://localhost:4572/"

The VM is running though:
vagrant@hashiqube0:~$ awslocal s3 ls

Could not connect to the endpoint URL: "http://localhost:4572/"

First, I REALLY appreciate this project.

Now, I am unsure whether this question belongs here or not but in case you're curious here are the details:

https://discuss.hashicorp.com/t/pointing-nomad-to-a-remote-docker-daemon-over-tcp/24997

So, would there be any value or interest in having this project have the ability for updating nomad to point to a docker daemon running elsewhere outside vagrant?

Waypoint doesn't work on new Apple chipsets, ref: hashicorp/waypoint#3572

Stay tuned...

Hello,

I launched the Hashiqube vagrant (Docker provider) successfully on a MacBook Pro M1 after adding the Consul DNS to /etc/resolver/consul as per instructions here: https://github.com/servian/hashiqube#consul-dns.

However DNS resolution fails with a timeout when I run nslookup vault.service.consul 10.9.99.10. If I run nslookup vault.service.consul it tries to resolve from the local IP 192.168.2.1.

If I try the dig command with the DNS IP 10.9.99.10 and port 8600, it resolves fine.

Because of that problem I am unable to launch the Fabio LB URLs in my browser such as http://vault.service.consul:9999/.

After each change to /etc/resolver/consul, I restarted the following : sudo killall -HUP mDNSResponder

Thank you for any assistance you can provide.

I got the following error trying to build the VM, I tried multiple times.

hashiqube0.service.consul: aws_s3_bucket.localstack-s3-bucket: Creating...
hashiqube0.service.consul: aws_s3_bucket.localstack-s3-bucket: Still creating... [10s elapsed]
hashiqube0.service.consul: aws_s3_bucket.localstack-s3-bucket: Still creating... [20s elapsed]
hashiqube0.service.consul: ╷
hashiqube0.service.consul: │ Error: Error creating S3 bucket: RequestError: send request failed
hashiqube0.service.consul: │ caused by: Put "http://localhost:4572/localstack-s3-bucket": dial tcp 127.0.0.1:4572: connect: connection refused
hashiqube0.service.consul: │
hashiqube0.service.consul: │ with aws_s3_bucket.localstack-s3-bucket,
hashiqube0.service.consul: │ on main.tf line 37, in resource "aws_s3_bucket" "localstack-s3-bucket":
hashiqube0.service.consul: │ 37: resource "aws_s3_bucket" "localstack-s3-bucket" {
hashiqube0.service.consul: │
hashiqube0.service.consul: ╵
hashiqube0.service.consul: ++++ awslocal s3 ls..
hashiqube0.service.consul:
hashiqube0.service.consul: Could not connect to the endpoint URL: "http://localhost:4566/"
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Hi there,

I have been trying to test provisioning to docker on an apple silicon Mac and I am getting an error. The command I used is:

vagrant up --provision --provider docker

and the error I get is:

hashiqube0.service.consul: ==> docker: Executing Ansible: ansible-playbook -e packer_build_name="docker" -e packer_builder_type=docker --extra-vars ansible_host=default ansible_connection=docker -e ansible_ssh_private_key_file=/tmp/ansible-key335928757 -i /tmp/packer-provisioner-ansible2601601172 /vagrant/hashicorp/packer/linux/ubuntu/playbook.yml hashiqube0.service.consul: docker: hashiqube0.service.consul: docker: PLAY [A demo to run ansible in a docker container] ***************************** hashiqube0.service.consul: docker: hashiqube0.service.consul: docker: TASK [Gathering Facts] ********************************************************* hashiqube0.service.consul: docker: ok: [default] hashiqube0.service.consul: docker: [WARNING]: Distribution Ubuntu 16.04 on host default should use hashiqube0.service.consul: docker: /usr/bin/python3, but is using /usr/bin/python2.7, since the discovered hashiqube0.service.consul: docker: platform python interpreter was not present. See hashiqube0.service.consul: docker: https://docs.ansible.com/ansible- hashiqube0.service.consul: docker: core/2.13/reference_appendices/interpreter_discovery.html for more information. hashiqube0.service.consul: docker: hashiqube0.service.consul: docker: TASK [Add a file to root's home dir] ******************************************* hashiqube0.service.consul: docker: changed: [default] hashiqube0.service.consul: docker: hashiqube0.service.consul: docker: TASK [Return all kv v2 secrets from a path] ************************************ hashiqube0.service.consul: docker: [DEPRECATION WARNING]: The default value for 'token_validate' will change from hashiqube0.service.consul: docker: True to False. This feature will be removed from community.hashi_vault in hashiqube0.service.consul: docker: version 4.0.0. Deprecation warnings can be disabled by setting hashiqube0.service.consul: docker: deprecation_warnings=False in ansible.cfg. hashiqube0.service.consul: docker: fatal: [default]: FAILED! => {"msg": "An unhandled exception occurred while running the lookup plugin 'hashi_vault'. Error was a <class 'ansible.errors.AnsibleError'>, original message: Invalid Vault Token Specified.. Invalid Vault Token Specified."} hashiqube0.service.consul: docker: hashiqube0.service.consul: docker: PLAY RECAP ********************************************************************* hashiqube0.service.consul: docker: default : ok=2 changed=1 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 hashiqube0.service.consul: docker: hashiqube0.service.consul: ==> docker: Provisioning step had errors: Running the cleanup provisioner, if present... hashiqube0.service.consul: ==> docker: Killing the container: 82cdc79e4953480826d199aa4649ec08888c6f4133dfe698d31bc6fb33ef1870 hashiqube0.service.consul: Build 'docker' errored after 36 seconds 905 milliseconds: Error executing Ansible: Non-zero exit status: exit status 2 hashiqube0.service.consul: hashiqube0.service.consul: ==> Wait completed after 36 seconds 906 milliseconds hashiqube0.service.consul: hashiqube0.service.consul: ==> Some builds didn't complete successfully and had errors: hashiqube0.service.consul: --> docker: Error executing Ansible: Non-zero exit status: exit status 2 hashiqube0.service.consul: hashiqube0.service.consul: ==> Builds finished but no artifacts were created.

Any ideas how I can work around it?

Hi, thank you for setting this project up.
I tried following the instructions, but I keep on getting this error:
running vagrant up --provision

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 94 of file VBoxManageHostonly.cpp

Any help is welcomed :)

http://localhost:3333/ is failing to load after setup.

I started to setup your solution and run into the issue that i have an other local IP range.

Meanwhile i saw that your IP range 10.x.x.x is hardcoded in some config files. I am thinking about to add a general pre-install .sh with variabels and requires in the config files.

What do you think about this solution in general?

Thank you in advance for some words about it to a advanced beginner ;-).

With best regards
Urs