-
Notifications
You must be signed in to change notification settings - Fork 25
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
Unzip problems with v1.8.0+ #22
Comments
@danherd, based on the error screenshot, wonder if the real error is:
Can you try using the |
Hi, That didn't work. The error from unzip is because it can't extract the zip file to the named directory. It is not a permission issue - it is simply that the version of unzip on this Docker image cannot handle the zip file: Whereas on my Ubuntu 20.04 machine: Here it is on the Docker machine using the same folder: Cheers, Dan |
Ahh, ok. I imagine an |
Unfortunately not! I think this version of busybox unzip has some sort of bug with the '-d' flag. It doesn't work, no matter what I pass (unless I pass '.', then it extracts the contents of the zip into the current folder) |
@danherd, thanks for all the information. I think we can add an option such as |
This is not a problem with the package, the zip lib does not create the directory and this was fixed in the latest version, if you update your zip lib you will see this fixed. |
But if the |
I am running into this same issue with the
and
and
|
Hi @toaomatis Just add this to an appropriate place in your Dockerfile:
That should fix it until the |
Thanks, this solved the problem (for now). Was not aware there was an additional / external |
I just did a PR adding the --use-ext option |
Hi,
This change has broken this tool for me.
I am using the php:7.1-fpm-alpine Docker image and trying to run the security-checker fails with the following error:
v1.7.0 works fine:
I presume the problem is that the version of unzip within BusyBox cannot handle the zip file:
Because it works fine on the unzip command in my host OS (Ubuntu 20.04
Cheers!
Dan
The text was updated successfully, but these errors were encountered: