-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No bug Cook section of a potluck install fails #297
Comments
Dang... Two questions: |
Hi @heyudude, I was in the middle of responding to you while you figured it out yourself. So I still kept my answer, but made it a bit more interesting by using layered images (so the resulting mariadb pot is a bit smaller):
If you want to build images in a clean environment, you could to take a look into https://github.com/bsdpot/potman (it's a bit of effort to get it going though). The flavours file system structure is due historic reasons (@pizzamig did this in the very beginning). Documentation improvements are welcome. |
Thanks for the quick answer! Thanks for the mariadb tips Do I need a Consul server instance? Seems so. I am still exploring all flavors of jails assistants, appjail, bastille, cbsd. This one is up to now the most easy to use, especially in the networking portion. It works out of the box using bridges and epairs. |
I don't know this specific image in detail, but looking at it, it seems like it registers node-exporter, mysql-exporter and mariadb services using consul, so they can be resolved using DNS (so it probably also works nicely with nomad). The exact requirements depend on the flavour and are documented in its README.md. |
Describe the bug
I get an error in every potluck I try to install.
Normal pot creation is fine
I run Freebsd 14.1
This the output:
and step 23-> 25 is:
To Reproduce
Steps to reproduce the behavior:
I expect the
tar -C /root/.pot_local -cf - . | tar -C /usr/local -xf -
failsExpected behavior
The pot is created and mariadb is installed
System configuration - if possible
/usr/local/etc/pot/pot.conf
(not needed I presume as the normal pots are created as I expect and work fine)
** If network related **
not related to network issues, a normal pot works fine with my network settings
The text was updated successfully, but these errors were encountered: