-
Notifications
You must be signed in to change notification settings - Fork 835
enhancement(ci): Add release docker image #844
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
base: main
Are you sure you want to change the base?
enhancement(ci): Add release docker image #844
Conversation
.github/workflows/docker.yml
Outdated
| name: docker | ||
| on: | ||
| push: | ||
| # TODO: Build on main? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The question here is, basically, should we build / push on merge? Right?
My first thought is: sure, why not? As long as we aren't bumping the latest tag.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EDIT: yes, this pushes only on main and tags.
|
This looks awesome! Thanks so much for taking this on! I have a few small requests, but they're just the cherry on top. If you've got time, that'd be great, but I really want to get this in. (p.s. this needs a signed-off-by :-) ) |
|
Also, looks like the new yamllint is mad at something :-p |
.github/workflows/docker.yml
Outdated
| name: docker | ||
| on: | ||
| push: | ||
| # TODO: Build on main? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
EDIT: yes, this pushes only on main and tags.
76a6cf4 to
1fa8df7
Compare
|
Do i have to signoff all commits? Or just in the PR body? |
3408e60 to
73df0e2
Compare
All commits :-). |
|
But we should squash this down to one or two commits before merging. |
|
|
||
| # This is the final, minimal container | ||
| FROM busybox as final | ||
| COPY docker-installer/install_cni_plugins.sh /script/install_cni_plugins.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You may need LABEL command to specify some of label, as github document mentioned, such as org.opencontainers.image.source
As I worked similar stuff in another repo, this org.opencontainers.image.source is required.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the tip. Any recommendation on which LABELs to add?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
managed to add all the org.opencontainers.image.xxx labels, hope i didn't miss anything.
will squash it down and sign once the PR is done :) |
|
oh yes, I was wondering about how to tie the release CI process with this docker image's binaries, so there is one source of binaries as discussed in #245 (comment). Can't seem to find out how the release process goes as far as looking around. |
2c28635 to
9abc4f6
Compare
|
squashed my commits down and signed off. i'm not sure what to do with whether previous work should be signed off too? |
|
@leojonathanoh can you rebase on |
|
sure, i'll do this tomorrow when i manage to get some time. |
9abc4f6 to
4772ad7
Compare
|
Any update on this PR @squeed ? Squash and merge and release 🚀 |
|
@leojonathanoh looks like you might need to rebase and fix any conflicts since it's taken this long for a merge :/ |
|
Sure 😄 |
4772ad7 to
747294f
Compare
Co-authored-by: Michael Wyraz <[email protected]> Signed-off-by: Leonard Jonathan Oh <[email protected]>
b57bc12 to
04a99b6
Compare
|
Passed on my fork, see leojonathanoh#1, where I have fork secrets that don't work on the CI here. Before merging, will need to remove the code marked with |
|
It's unfortunate that this as been pending so long, it seems like the maintainers are ignoring this or don't find value in this PR 😭 |
|
it's fine 😄 perhaps it will get merged. Guess not many in the community need a docker image for updating plugins 😬 |
|
@leojonathanoh hello, sorry things get lost in the shuffle! The best way is to join the weekly sync and put an item on the agenda! Sorry for the delay! |
Hello, I was the author of the initial request (#245). After a few years I'm back to "multus-cni" and had the hope this is meanwhile merged :-( |
Thanks for your previous work. Hope to see this merged too 😄 |
|
So... what exactly is the holdup on this? It seems like no one wants to review. We get that projects are time consuming, but not providing the means to successfully contribute with this PR while accepting others that also advance the project doesn't sit well... |
|
They're hoping for people to join their weekly meetings to discuss this. Honestly, I don’t see how a change like this couldn't be handled asynchronously. 🙄 |
|
Hello, any chance of this PR to be finally merged? |

This adds a multiarch docker image, based on previous work in #245.
Since I'm not an approved collaborator on this repo with read access to repository secrets, the CI will not be able to login to Docker Hub and push images. To show it works, I'm building the same branch on my fork PR to demonstrate that it works. leojonathanoh#1
TODO
Implements #806
Signed-off-by: Leonard Jonathan Oh [email protected]