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 client: nomad fails to deploy zip archives if they contain sub folders #1028
Comments
This might be the same bug as hashicorp/go-getter#11. It's been fixed in go-getter library but nomad's vendored go-getter is not yet up to date. |
Just vendored the update in 663b04f. Could you please try on master again? |
@dadgar, This broke the build for me when i do
|
In |
Nice! I am going to close this issue then! Sorry about the build problem! |
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.3.1
Nomad v0.3.2-dev ('270da7a60ccbf39eeeadc4064a59ca06bf9ac6fc+CHANGES')
Operating system and Environment details
Windows Server 2012 R2 Datacenter
Issue
When running a zip archive on windows, the nomad client fails to unzip the archive properly and fails to start the task. This seems to be triggered by the archive zip folder having sub-folders. It appears (although the logs don't say anything) that the unzip process fails mid-way through unzipping the archive - as there is an incomplete set of files in the alloc folder.
Reproduction steps
The text was updated successfully, but these errors were encountered: