-
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
windows docker logs are empty #5979
Comments
Thanks for the report @ilyaiqoqo , we'll investigate and post an update |
hey @ilyaiqoqo, I've just tried to reproduce this on current master, on Windows Server 2019 with the same jobspec and received the expected logs: I got the same result running nomad both as administrator and as a regular user. (The logs cli is running inside the WSL shell for convenience, but the agent is running in a regular Windows Powershell) Based on the behavior you're seeing though, it looks like we're failing to stat the path we wish to use for logs for (I would guess permissions related?) reasons and failing to handle that correctly. I've just created the Thanks! |
using
|
@ilyaiqoqo Hey! - So it looks like this bug is caused by a regression in go1.11.x (related to golang/go#29119), but is fixed in go1.12, could you rebuild with go1.12 to confirm? |
@endocrimes compiling with go1.12.7 fixed the error |
@ilyaiqoqo thanks! - I just opened #5990 as a workaround for the actual 0.9.4 release as we can't upgrade minor go versions in a patch release. Thanks for helping to confirm the underlying issue though. Have a great day 👋 |
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.4-dev (87d716e)
Operating system and Environment details
windows 10 1809
Docker version 19.03.0-rc2, build f97efcc
Issue
Allocation logs are empty in latest nomad version. but it works fine on v0.9.3 tag
Reproduction steps
run job on windows
nomad agent -dev
expected result:
actual result is empty log and exception in the log
Job file (if appropriate)
Nomad Client logs (if appropriate)
PS C:> .\nomad-latest.exe agent -dev
==> No configuration files loaded
==> Starting Nomad agent...
==> Nomad agent configuration:
==> Nomad agent started! Log data will stream in below:
The text was updated successfully, but these errors were encountered: