-
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
simple exec (no cgroups, docker or resource isolation) #213
Comments
There is one https://nomadproject.io/docs/drivers/exec.html There are even Qemu and JVM drivers. |
Every time I execute a job with Example:
gives
and makes a new mount point on the box
and umounts before
after
|
Hey, Would you mind describing your environment? The mounts are a bit odd because they get cleaned up with the allocation is destroyed. This is hours after the job finishes which in a production environment gives you time to look at the logs or ship them. But when running locally it is undesirable. We will work on that. BTW the stdout and stderr logs can be found in the tasks local directory. This can be found at /nomad_alloc_dir/alloc_id/task_name/local/task_name.stderr/stdout |
Hi, I'm running the 5 x nomad servers and 7 x nomad clients - with v0.1.0 - each on its own dedicated vm. both the nomad servers and nomad clients are running inside a QEMU / KVM instance running Debian 7.8 with a custom 4.0.6 kernel Is it possible to make a executor that won't touch anything, but simple exec a command without any server modifications ? :) I'm not looking for nomad for resource isolation, but simply a distributed executor in place of supervisord - which have plenty of pain points for us currently. example fstab
|
From my understanding of the code, the exec driver relies uses the executor to run your task within a per-task chroot. It will make some mounts available within this chroot but most won't be. Which mounts are accessible is currently not configurable. I have the same requirement as you and I'd be willing to attempt to write the code if there's consensus on a design that's likely to be accepted. |
+1 simple exec (no cgroups, docker or resource isolation) for instance, to run "puppet apply" command in the hosts. |
Just as an update, this is something we plan to support. |
We now have a raw_exec driver! |
Ensure InstallSnapshot always consumes the snapshot from the stream.
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. |
hi,
a nice feature would be to have a very simple exec driver, that just runs a command
no fancy docker, cgroups or resource isolation - just running a command
would allow me to replace supervisord with nomad, and get a lot of the features I'm missing from supervisor backed right into nomad
The text was updated successfully, but these errors were encountered: