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

vendor: bump runc to 1.1.0 #3048

Merged
merged 1 commit into from
Jan 21, 2022
Merged

vendor: bump runc to 1.1.0 #3048

merged 1 commit into from
Jan 21, 2022

Conversation

kolyshkin
Copy link
Contributor

Brought to you by

go get -d github.com/opencontainers/runc@latest
go mod tidy
cd cmd
go get -d github.com/opencontainers/runc@latest
go mod tidy

Brought to you by

	go get -d github.com/opencontainers/runc@latest
	go mod tidy
	cd cmd
	go get -d github.com/opencontainers/runc@latest
	go mod tidy

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
@k8s-ci-robot
Copy link
Collaborator

Hi @kolyshkin. Thanks for your PR.

I'm waiting for a google member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kolyshkin
Copy link
Contributor Author

@bobbypage can you cut a release once this PR lands, so I can do the same bump in kubernetes?

@kolyshkin
Copy link
Contributor Author

@bobbypage PTAL 🙏🏻

@bobbypage
Copy link
Collaborator

/lgtm

@bobbypage bobbypage merged commit 68d9919 into google:master Jan 21, 2022
@bobbypage
Copy link
Collaborator

bobbypage commented Jan 21, 2022

@bobbypage can you cut a release once this PR lands, so I can do the same bump in kubernetes?

Usually we cut new cAdvisor release prior to k/k release, so I was planning on cutting next 0.44 release closer to when k8s 1.24 will be released. I think we should be able to update update runc in k/k without also updating cAdvisor tag or is that not the case?

@kolyshkin
Copy link
Contributor Author

I think we should be able to update update runc in k/k without also updating cAdvisor tag or is that not the case?

Due to API changes in runc, I think it is not possible. Currently, in kubernetes/kubernetes#107149 I have updated cadvisor to commit a3b5f4f, but an unreleased version does not look good in go.mod.

@kolyshkin
Copy link
Contributor Author

I think we should be able to update update runc in k/k without also updating cAdvisor tag or is that not the case?

Due to API changes in runc, I think it is not possible.

To clarify -- attempting this will result in compilation errors.

@bobbypage
Copy link
Collaborator

ah, thank you for clarification, it makes sense due to the changes you made in #3031

I will cut a new release then to unblock updating runc update in k/k. Thanks!

@kolyshkin
Copy link
Contributor Author

I will cut a new release then to unblock updating runc update in k/k. Thanks!

Filed #3055 to remind / track this, thanks @bobbypage!

@kolyshkin kolyshkin deleted the runc-1.1 branch February 3, 2022 16:20
ehashman added a commit to ehashman/kubernetes that referenced this pull request Mar 28, 2022
This updates vendored runc/libcontainer to 1.1.0,
and google/cadvisor to a version updated to runc 1.1.0
(google/cadvisor#3048).

Changes in vendor are generated by (roughly):

        ./hack/pin-dependency.sh github.com/google/cadvisor v0.44.0
        ./hack/pin-dependency.sh github.com/opencontainers/runc v1.1.0
        ./hack/update-vendor.sh
        ./hack/lint-dependencies.sh # And follow all its recommendations.
        ./hack/update-vendor.sh
        ./hack/update-internal-modules.sh
        ./hack/lint-dependencies.sh # Re-check everything again.

Co-Authored-By: Kir Kolyshkin <kolyshkin@gmail.com>
k8s-publishing-bot pushed a commit to kubernetes/kubectl that referenced this pull request Mar 29, 2022
This updates vendored runc/libcontainer to 1.1.0,
and google/cadvisor to a version updated to runc 1.1.0
(google/cadvisor#3048).

Changes in vendor are generated by (roughly):

        ./hack/pin-dependency.sh github.com/google/cadvisor v0.44.0
        ./hack/pin-dependency.sh github.com/opencontainers/runc v1.1.0
        ./hack/update-vendor.sh
        ./hack/lint-dependencies.sh # And follow all its recommendations.
        ./hack/update-vendor.sh
        ./hack/update-internal-modules.sh
        ./hack/lint-dependencies.sh # Re-check everything again.

Co-Authored-By: Kir Kolyshkin <kolyshkin@gmail.com>

Kubernetes-commit: 07af1bab707c16c7fde936dca6579002405159ac
muyangren2 pushed a commit to muyangren2/kubernetes that referenced this pull request Jul 14, 2022
This updates vendored runc/libcontainer to 1.1.0,
and google/cadvisor to a version updated to runc 1.1.0
(google/cadvisor#3048).

Changes in vendor are generated by (roughly):

        ./hack/pin-dependency.sh github.com/google/cadvisor v0.44.0
        ./hack/pin-dependency.sh github.com/opencontainers/runc v1.1.0
        ./hack/update-vendor.sh
        ./hack/lint-dependencies.sh # And follow all its recommendations.
        ./hack/update-vendor.sh
        ./hack/update-internal-modules.sh
        ./hack/lint-dependencies.sh # Re-check everything again.

Co-Authored-By: Kir Kolyshkin <kolyshkin@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants