Skip to content
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

Closed
iliyan-s-petkov opened this issue Jan 9, 2023 · 7 comments · Fixed by #152

Comments

@iliyan-s-petkov
Copy link

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

@neersighted
Copy link
Contributor

Looks like a duplicate/special case of #140 where I forgot to set the execute bit when manually preparing the archives. @evol262, do you want to upload new builds performed using your usual method?

@afbjorklund
Copy link
Contributor

afbjorklund commented Jan 9, 2023

While you are at it, you might want to remove the user as well.

tar --owner=0 --group=0

And what about the linux ? It's a wild wild west, this business...

crictl-v1.26.0-linux-amd64.tar.gz (now where did that v come from?)

@evol262
Copy link
Contributor

evol262 commented Jan 9, 2023

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 linux because linux is the presumed default, and "not-linux (sort-of)" ends up with annotations about what it is. We could change that, too, but it doesn't make the wild wild west any less wild. We don't use CGO, but glibc, cosmopolitan libc, musl libc, gccgo, and a huge matrix of "Linux but different" options are also possible.

@afbjorklund
Copy link
Contributor

afbjorklund commented Jan 9, 2023

it doesn't make the wild wild west any less wild.

And still prefer people to use the packages, anyway.

@afbjorklund
Copy link
Contributor

Do we think it's worth the time to re-build this one?

Fixing it for the future sounds like the right approach

@evol262
Copy link
Contributor

evol262 commented Jan 9, 2023

Rebuild it is then.

@afbjorklund
Copy link
Contributor

I meant "for next time" (release), but sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants