-
Notifications
You must be signed in to change notification settings - Fork 206
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
Support for Flatcar Linux #66
Comments
/set title: Support for Flatcar Linux |
Hi @mdaniel thank you for your interest. You'll have to bring me up to speed here, as I don't use that specific distro. What path is used for Flatcar Linux and what would prevent you from creating Alex |
/usr is read-only in Flatcar Container Linux (like CoreOS): |
How would people normally run processes or install software? Does it only run containers, or is there somewhere on the filesystem that's fair game? |
Given that this is Container Linux, the recommended way of running things on Flatcar is to use containers. Can An alternative would be, to store the binary in Then, if path in sudo mkdir /opt/bin
sudo mount --bind /opt/bin /usr/local/bin This can also be automated with Ignition. |
We could accept a PR to install to a specific location. What other issues do you envisage? Perhaps try the bind mount and see if that's enough? |
If only a binary is needed, I guess no other issues.
Don't hesitate to write us if you find any other issues :-) |
Thanks for everyone weighing in; while the
I do appreciate that command-line flags or config files may go against the ethos of "download binary, get faasd" but their flexibility allows the software to work in a lot more situations I just wanted to report back; I guess for now I'll just hack on the source to fix all the hard-coded paths until it starts to work, and then decide if I've made too much of a mess to PR it :-) 1 = AIUI, customer-provided systemd units should go into |
Happy to take a PR for that specific change, along with changes to the rest of the repo/terraform and bash. |
Which paths are the offending ones? I'd like to see: a list of possible solutions, and one preferred solution. |
writing to systemd units to Other options could be overly mounts, but that feels like a one-off, like the bind mounting. |
What is the ideal way we should deploy a binary and have some state when using Flatcar @vbatts? K3s will be similar in that it has an /etc/ folder and a /var/lib/ folder and a binary in /usr/local/bin/ |
@alexellis sorry for the late response. Not sure I understand your question, |
Expected Behaviour
faasd install
does whatever it was trying to do without errorCurrent Behaviour
Possible Solution
Instead of hard-coding the path, do the golang equivalent of
the_file="$(cd $(dirname "$0") && pwd)/$(basename "$0")"
isSteps to Reproduce (for bugs)
vagrant install vagrant-ignition
Vagrantfile
below into the current directoryvagrant up
faasd install
errorContext
I was just interested in running
faasd
to see what it was like, and our fleet of machines is already runningcontainerd
on FlatcarYour Environment
OS and architecture:
Versions:
The text was updated successfully, but these errors were encountered: