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

go.mod: Update gvisor_vsock_tap dependency #3703

Merged
merged 1 commit into from
Jun 12, 2023

Conversation

praveenkumar
Copy link
Member

Updating to containers/gvisor-tap-vsock@b79db04 which resolve #3643 issue.

Fixes: Issue #3643

@openshift-ci openshift-ci bot requested review from cfergeau and evidolob June 9, 2023 10:19
@openshift-ci
Copy link

openshift-ci bot commented Jun 9, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from praveenkumar. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

github.com/ProtonMail/go-crypto v0.0.0-20230217124315-7d5c6f04bbb8
github.com/YourFin/binappend v0.0.0-20181105185800-0add4bf0b9ad
github.com/asaskevich/govalidator v0.0.0-20210307081110-f21760c49a8d
github.com/cavaliergopher/grab/v3 v3.0.1
github.com/cheggaaa/pb/v3 v3.1.0
github.com/containers/gvisor-tap-vsock v0.5.0
github.com/containers/gvisor-tap-vsock v0.6.2-0.20230609094134-b79db04d368e
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer to stick to release gvisor-tap-vsock versions.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cfergeau once we have the next release cut we will use it but as of now we have a old release.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this fixes a critical bug on CRC, it'd be good to vendor a released gvisor-tap-vscok but since we don't have a newer release with the needed changes, we can do that when there's new release for gvisor-tap-vsock

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we are the upstream for gvisor-tap-vsock, getting a new release is relatively easy... ;)

@openshift-ci
Copy link

openshift-ci bot commented Jun 9, 2023

@praveenkumar: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-crc 215c0ac link true /test e2e-crc

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@praveenkumar
Copy link
Member Author

/retest

@praveenkumar praveenkumar added the has-to-be-in-release This PR need to go in coming release. label Jun 12, 2023
@anjannath anjannath merged commit 5684cc2 into crc-org:main Jun 12, 2023
@mmurhamm
Copy link

@praveenkumar , is there a patch I can use or do I need to wait for the next release of crc? Thanks for fixing this.

@anjannath
Copy link
Member

@mmurhamm crc-2.21.0 will be released soon (1-2 days) otherwise you can build from current master, following this guide: https://github.com/crc-org/crc/blob/main/developing.adoc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has-to-be-in-release This PR need to go in coming release.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Issues with DNS lookups from within the container
4 participants