-
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
Nomad Logs doesn't return logs on short running containers. #2457
Comments
Hey I couldn't replicate this:
Job:
I believe you may just be missing |
I can reproduce this, logs for short running param jobs are all missing |
Also seem to notice this behavior |
v 0.9.2 also affected |
same for 0.10.0-dev |
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 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.4
Operating system and Environment details
Ubuntu 16.04 LTS on AWS
Issue
Fast running docker containers (a few seconds long) do not leave logs accessible with the nomad logs command. Also, the container never appears in a docker ps -a on the node. The container in question (myena/consul-backinator) just runs a simple command. The logs are, however, accessible on the node at /var/lib/nomad/alloc/[allocation-id]/alloc/logs/consul-backinator.stderr.0
Reproduction steps
Run the nomad job file below:
Nomad Server logs (if appropriate)
Nomad Client logs (if appropriate)
Job file (if appropriate)
The text was updated successfully, but these errors were encountered: