-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Ability to run the command directly from a mounted hosted volume #11781
Comments
Ok I did some digging and it is possible with some workarounds see:
Would be cool to have this behavior build-in somehow (like disable_checker = true on the exec driver) |
Hi @wojciak Thanks for all your work and thoughts on this. We'll review this suggestion, and think about feasibility, etc. From there we'll update this issue with next steps. Derek |
Hi @wojciak effectively you're running into the exact same issue I commented on here #11690 (comment):
commands = "/bin/sh"
args = ["-c", "exec /foo/var"] The source of this issue is arising from libcontainer and not something we have control over in Nomad. It might be possible to do in some future task drivers not based on libcontainer but right now that's virtually all of them. I'm going to keep this issue open but I want to be honest with you that I would not expect to be implemented anytime soon. Give the workaround I've proposed here as try for your use case. |
PR up for this in #14851. As it turns out, it's not a libcontainer limitation but something we were doing around setting binaries as executable. |
#14851 has been merged and will ship in the next regular release of Nomad (likely 1.4.3) |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Proposal
I'd like to use an fsx mount as a hosted volume for my nomad cluster, the issue is that I cannot run any apps from it, because the volume is not mounted by the time of the app execution.
The proposal is to make sure (or add a lifecycle toggle) that when the config.command stanza is run, all the hosted volume mounts are resolved.
Use-cases
This is very useful for hotfix deployment and any ci/cd pipeline
Attempted Solutions
Prestart lifecycle hook with a different task, poststart lifecycle hook - as all tasks have their own allocations this still won't make the volume available when the config.command stanza is run
The text was updated successfully, but these errors were encountered: