Open cweimann opened 9 months ago
Hi. I have the same version of consul and no problem with that.
Can you please share /usr/local/etc/consul.d/minipot-agent.json
and the output of the command grep ^consul /etc/rc.conf
minipot
is also going to configure the system to write logs in /var/log/consul/consul.log
@cweimann I tried here as well and it worked out of the box. So maybe the environment is polluted with other configurations or something about the setup causes some hashicorp fingerprinter to go wrong (#wildspeculation). Maybe sharing the output of ifconfig
and cat /etc/rc.conf
and cat /etc/pf.conf
could help to figure out what's going on.
Doing a fresh FreeBSD install.
"pot vnet-init" doesn't work. I think that ought to be "pot vnet-start". Ok, I found something. After "pot de-init" the bridge is still there and minipot-init must get confused by that. Skipping that and going straight to minipot-init and I now get consul and traefik but no nomad. Still looking....
Ok, this commit to nomad's startup script on FreeBSD broke it.
Specifically the nomad_command setting. I added -data-dir=${nomad_dir} back in. They way they have changed it your setting of nomad_args winds up removing the nomad data-dir setup and nomad won't start.
So, my first problem was that I did the klara bits testing pot and wound up with a bridge that confused minipot-init. After fixing that I found a problem with the FreeBSD nomad package.
I can only presume things worked for you because you were didn't do the pot test bits and had packages from before 2023/09/22.
Knowing it worked for you was helpful :).
ok... nginx.job doesn't work. It just spins on "Deployment "c5ef80af" in progress..." It seems that it uses image = "https://pot-registry.zapto.org/registry/" and that hostname dosen't resolve.
@cweimann I'd suggest to use the job description from
https://github.com/bsdpot/nomad-pot-driver?tab=readme-ov-file#complete-job-example
I tried this on both FreeBSD 14.0 and 13.2. I suspect the problem is the consul config (new version of consul) and nomad doesn't start because there is no consul running. The below run is from the FreeBSD 14.0 box.