-
Notifications
You must be signed in to change notification settings - Fork 300
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
Execute permission for cri-dockerd/cri-dockerd not set in cri-dockerd-0.3.0.amd64.tgz #148
Comments
While you are at it, you might want to remove the user as well.
And what about the crictl-v1.26.0-linux-amd64.tar.gz (now where did that |
There's a pending PR where we can do the "re-vendor upstream k8s deps" dance (which is always really fun) which will end up in a new release. Do we think it's worth the time to re-build this one? There's no |
And still prefer people to use the packages, anyway. |
Fixing it for the future sounds like the right approach |
Rebuild it is then. |
I meant "for next time" (release), but sure. |
Hello and happy new year!
In the previous releases of the cri-dockerd (amd64.tgz), the execute flag was set for the cri-dockerd/cri-dockerd.
In 0.3.0 the execute flag is no longer set:
$ tar -tvf cri-dockerd-0.3.0.amd64.tgz
drwxr-xr-x 0 neersighted wheel 0 Dec 22 18:18 cri-dockerd/
-rw-r--r-- 0 neersighted staff 54652001 Dec 22 18:16 cri-dockerd/cri-dockerd
Is that by intention?
With the execute flag missing, during installation it has to be set, adding one more step to the installation process.
For reference:
$ tar -tvf ./cri-dockerd-0.2.1.amd64.tgz
drwxr-xr-x 0 rbarry rbarry 0 May 25 2022 cri-dockerd/
-rwxr-xr-x 0 rbarry rbarry 52331990 May 25 2022 cri-dockerd/cri-dockerd
The text was updated successfully, but these errors were encountered: