-
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
Invalid config format is silently ignored #735
Comments
I'm not sure if this is the problem but your config is not valid JSON. It looks like you have mixed HCL syntax with JSON syntax. I'm not sure how this will be parsed.
should be
Note the |
@cbednarski thank you for spotting the error.
Should I close this issue and open a new one for the config parser? Thanks! |
All the info is here I will just change the title. |
Fixed via #910 |
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. |
There is a bug in the config syntax, which looks like a mix between HCL and JSON. Rather than emitting an error, Nomad appears to silently drop some of the config information.
Nomad should complain that it cannot parse the config.
-- cbednarski
Like most of the people around here once I've found the tools you guys make I completely fall in love with them :).
I would like in the future to deploy a cluster built with Nomad, Vault, Consul and Consul Template on top of Docker.
So I started playing around with them. And I thought I would take one of our project and construct a development environment on local machines with the help of boot2docker, Nomad and Consul, slowly integrating the other tools.
First approach was to create custom docker images for consul and nomad and run them with
--net=host
. Said and done. But then I have found about #150, precisely that I can't mount volumes in containers. I would require them to mount code from the local machine inside the container and to mount a data directory for the database.Reading around I came to the conclusion that I can use
raw_exec
driver withcommand=docker
andargs=["-v ...",]
.So I have created a custom boot2docker.iso with nomad inside.
I have the following agent configuration:
Nomad logs in
/var/lib/boot2docker/nomad.log
. I can see the following logs when I start nomad:As per the log above the
raw_exec
driver is not loaded onlydocker
andexec
.I have a
dev.nomad
job file that looks like:Running it with
nomad run dev.nomad
gives the following output on the client:mobum-django-app
failed because it couldn't find a node which has driverraw_exec
. As expected I would say :).I didn't stop here so I switched
raw_exec
withexec
for taskmobum-django-app
and now I have the following output on the client:But the
mobum-django-app
task failsto configure task directory
as per the nomad logs.Would the situation change if I load raw_exec? How can I load it for testing purposes? Thanks.
The text was updated successfully, but these errors were encountered: