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
Recently I got an error when I try to push an app to IronFoundry:
{"cmd":"unzip","args":["C:/IronFoundry/dea_ng/staging/d20130828-1912--8hs0cx/app.zip","@root@/tmp/unstaged" ]}]","exit_status":1,"stdout":"","stderr":"Wrong Central Directory signature\r\n"},"thread_id":3296232,"fiber_id":184674
36,"process_id":1912,"file":"C","lineno":0,"method":"223"}
I digged into the problem and found out that the app.zip coming from the cloud controller is a Zip64 file. The library used by the IronFoundry warden to extract the archive (SharpZipLib) seems to have issues with Zip64 archives.
I currently use a workaround such that I force the cloud controller (in lib/cloud_controller/app_package.rb) to not use Zip64 (using the -fz- option). Then it works without problem.
I just wonder why this happens now (I now have v138 of CF) where it didn't happen before. I can live with the workaround, I just wanted to make you aware of this issue.
-- Thomas
The text was updated successfully, but these errors were encountered:
Recently I got an error when I try to push an app to IronFoundry:
{"cmd":"unzip","args":["C:/IronFoundry/dea_ng/staging/d20130828-1912--8hs0cx/app.zip","@root@/tmp/unstaged" ]}]","exit_status":1,"stdout":"","stderr":"Wrong Central Directory signature\r\n"},"thread_id":3296232,"fiber_id":184674
36,"process_id":1912,"file":"C","lineno":0,"method":"223"}
I digged into the problem and found out that the app.zip coming from the cloud controller is a Zip64 file. The library used by the IronFoundry warden to extract the archive (SharpZipLib) seems to have issues with Zip64 archives.
I currently use a workaround such that I force the cloud controller (in lib/cloud_controller/app_package.rb) to not use Zip64 (using the -fz- option). Then it works without problem.
I just wonder why this happens now (I now have v138 of CF) where it didn't happen before. I can live with the workaround, I just wanted to make you aware of this issue.
-- Thomas
The text was updated successfully, but these errors were encountered: