-
Notifications
You must be signed in to change notification settings - Fork 2k
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
failed to decode driver config: readContainerLen: Unrecognized descriptor #5680
Comments
Hi @JeffreyVdb, Sorry you hit this. The reason the job validates but fails at runtime is because the migration to plugins in 0.9 introduced a regression where servers can no longer validate task's driver That error message is also particularly useless and is something we intend to improve in future releases. The error is that you're using I filed a new issue for fixing the error message when using an undefined variable:
I'm going to close this in favor of #5694, but please feel free to reopen if you feel like I missed something. Thanks for the report and sorry for the regression. |
This upgrades hcl2 library dependency to pick up hashicorp/hcl2#113 . Prior to this change, parsing and decoding array attributes containing invalid errors (e.g. references to unknown variables) are silently dropped, with `cty.Unknown` being assigned to the bad element. Rather than showing a type/meaningful error from hcl2, we get a very decrypted error message from msgpack layer trying to handle `cty.unknown`. This ensures that we propagate diagnostics correctly and report meaningful errors to users. Fixes #5694 Fixes #5680
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. |
Nomad version
Nomad v0.9.1 (4b2bdbd)
Operating system and Environment details
Issue
When running an HCL file, decoding driver config fails with the error message:
Nomad validate returns that the file is valid however:
Reproduction steps
Job file (if appropriate)
Nomad Client logs (if appropriate)
Nomad Server logs (if appropriate)
The text was updated successfully, but these errors were encountered: