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

rancher-agent-2.10/2.10.0-r0: cve remediation #36778

Closed

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Dec 13, 2024

Copy link
Contributor Author

octo-sts bot commented Dec 13, 2024

Gen AI suggestions to solve the build error:

• Detected Error: "Failed to running update. Error: package github.com/docker/docker with version 'v24.0.9' is already at version v25.0.6+incompatible"

• Error Category: Version/Dependency

• Failure Point: go/bump step in the pipeline attempting to update github.com/docker/docker dependency

• Root Cause Analysis: The go/bump step is trying to downgrade github.com/docker/docker from v25.0.6+incompatible to v24.0.9, which is not allowed by Go's module system

• Suggested Fix:

  1. Remove the github.com/docker/[email protected] from the go/bump step
  2. Update the go/bump step to:
  - uses: go/bump
    with:
      deps: github.com/golang-jwt/jwt/[email protected] github.com/go-jose/go-jose/[email protected] golang.org/x/[email protected]

• Explanation:

  • Go's module system prevents downgrading dependencies to older versions
  • The existing module already has a newer version (v25.0.6+incompatible)
  • Removing the explicit version constraint will allow the build to proceed with the existing compatible version

• Additional Notes:

  • If v24.0.9 is specifically required, you may need to use replace directives instead
  • Consider testing the build with the newer docker client version as it should maintain backwards compatibility
  • The +incompatible suffix indicates this is a v0/v1 module being used at a v2+ version

• References:

@hbh7 hbh7 self-assigned this Dec 13, 2024
@hbh7
Copy link
Member

hbh7 commented Dec 14, 2024

The docker CVE is going to take additional work to fix since it's got a weird replace setup (replaced and also required). I tried for a while to get it to work but I didn't get anywhere with it.

replace (
       ...
        github.com/docker/docker => github.com/docker/docker v20.10.27+incompatible // rancher-machine requires a replace is set
        ...
)
...
require (
        ...
        github.com/docker/docker v25.0.6+incompatible
        ...
)
...

@hbh7 hbh7 removed their assignment Dec 14, 2024
@hbh7 hbh7 added the help wanted Extra attention is needed label Dec 14, 2024
@octo-sts octo-sts bot added bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. manual/review-needed labels Dec 14, 2024
@cmwilson21 cmwilson21 removed the help wanted Extra attention is needed label Dec 17, 2024
@cmwilson21
Copy link
Member

Removing the help wanted label since @kbsteere picked it up. If you run into any issues, please feel free to re-add the label! 👍

@kbsteere
Copy link
Contributor

@cmwilson21 @powersj @philroche can this be closed since we are addressing the issues in this cve-remediation? #35370

@powersj
Copy link
Contributor

powersj commented Dec 17, 2024

@kbsteere I think so, but let's have @philroche confirm.

@philroche
Copy link
Member

Yes. Closing. Looks like automation is creating duplicate remediations though.

@philroche philroche closed this Dec 18, 2024
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.

5 participants