You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This race condition was fixed in PR #2007 and released in Nomad 0.5.1. I would recommend upgrading to Nomad 0.5.6 if possible as it is the most stable release of the 0.5 series.
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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
If you have a question, prepend your issue with
[question]
or preferably use the nomad mailing list.If filing a bug please include the following:
Nomad version
Nomad v0.5.0
Operating system and Environment details
Running on CoreOS
Issue
Apparently a failing task was running and got restarted very frequently. At some point a nomad node started responding because it had a panic.
The task was failing due to a panic in runc. The docker image is a minimal golang image that is built
FROM scratch
but had an entrypoint. The doker image was built from https://github.com/mildred/hello/tree/1aa0b61eacc483eb7128bc7725d5d122cd8b8714The job was showing the following logs repeatedly on its stderr:
Reproduction steps
This is probably very difficult to reproduce
Nomad Client logs
Job file (if appropriate)
The text was updated successfully, but these errors were encountered: