-
Notifications
You must be signed in to change notification settings - Fork 64
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
Won't compile on FreeBSD 14.0 with the default GNUmakefile #370
Comments
This compiles with the altered |
@bretton we might be willing to accept a PR but none of the folks working on the team have the bandwidth to test FreeBSD as a platform (much the same as with Nomad core), so it'd really be up to you to contribute that. |
PEBKAC error, the issue can be solved by ensuring
when done copy the binary
|
Hi @bretton Trying to setup nomad client with nomad-driver-podman on Freebsd host, with the help of your previous comment was able to start the nomad client at least, but still facing such error - Thanks. |
Make sure the podman service is started
I have an example ansible playbook for setting up a test environment to demonstrate feasibility of podman containers on FreeBSD with nomad. in particular this bit for podman-nomad-driver, however the podman service is started in a different role. |
Thanks @bretton for such swift answer and for sharing code. I made sure that podman service is running, but it still throwing the same error. Thank you. |
@OneOfTheJohns check nomad client is running as root user? in my example playbook I have the nomad client service configured with
|
@bretton thanks once again for another tip, but still same error, as i was already running nomad client using root user. Will try to explain all steps i have taken so far in troubleshooting: To install podman, i followed https://podman.io/docs/installation#installing-on-freebsd-140Checked if podman service is running
Checked if permissions of the client directory are set (accodring to https://discuss.hashicorp.com/t/nomad-with-podman-driver-setup-issues/69609/6) they should be 0700
The contents of the client.hclroot@:~ # cat /usr/local/etc/nomad/client.hcl
Im starting the nomad client using root user
I tried to search for the "run/podman/podman.sock" anywhere on the filesystem, but it seems that it was not created?
So by now im quite confused, why would the podman socket not be open, if the service is running (if of course the service im running is not broken?). Still havent tested your ansible playbook though (only looked at it).All of the logs im getting :
|
@OneOfTheJohns my nomad is setup to use /var/tmp/nomad with freebsd pkg install
and /usr/local/libexec/nomad/ only has a plugins directory with contents from the nomad-driver-podman setup
my /usr/local/etc/nomad/client.hcl
|
Thanks @bretton for your time, i finally fixed my issue.
|
I can't get this to build on FreeBSD 14.0 without some changes as covered below. They're rough and probably not the right way to do it. Can you look at making it more freebsd friendly please? I don't know how well it runs yet, however improving compile process is a start. I have podman containers working on the OS.
ERRORS
Versions
SOLUTION:
edit Makefile and make the following edits
then run
when done
The text was updated successfully, but these errors were encountered: