-
Notifications
You must be signed in to change notification settings - Fork 94
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
Chore: need to bump oras-go to v2 to unblock k8s updates #1317
Comments
@xavpaice when I upgraded to following:
..reproducing the steps brought me here:
so then I proceeded to upgrade and then Didn't need to upgrade |
#1295 is likely blocked too - let's get that tested out |
k8s.io has been updated, the errors in #1295 match this error (and many examples). See https://github.com/helm/helm/pull/12310/files for an example of how Helm updated the dependency. See https://github.com/oras-project/oras-go/releases/tag/v2.0.0 for some more info on what changed when they released v2. |
Signed-off-by: Archit Sharma <[email protected]>
After adding/reverting a few migrations for OCI compliant pulls and the new v2 SDK (WIP #1339), I'm still getting the docker incompatibility issues because helm/helm#12310 has not yet been merged into helm (and regardless, that PR is not complete it seems as some parts of helm still use v1 in it). # go mod graph | grep oras
helm.sh/helm/[email protected] oras.land/[email protected]
# go mod why oras.land/oras-go/v1
(main module does not need package oras.land/oras-go/v1)
# go mod why oras.land/oras-go/v2
github.com/replicatedhq/troubleshoot/pkg/oci
oras.land/oras-go/v2 Ignoring the current pull.go WIP migration errors, the build slides back into # make build
# pkg/oci/pull.go:68:2: too many errors
make[1]: *** [collect] Error 1
# oras.land/oras-go/pkg/auth/docker
../../../../go/pkg/mod/oras.land/[email protected]/pkg/auth/docker/login.go:86:39: cannot use remote (variable of type *"github.com/docker/docker/registry".Service) as "github.com/docker/docker/registry".Service value in argument to c.loginWithTLS
# oras.land/oras-go/pkg/auth/docker
../../../../go/pkg/mod/oras.land/[email protected]/pkg/auth/docker/login.go:86:39: cannot use remote (variable of type *"github.com/docker/docker/registry".Service) as "github.com/docker/docker/registry".Service value in argument to c.loginWithTLS
make[1]: *** [preflight] Error 1
make[1]: *** [analyze] Error 1
make: *** [build] Error 2 Therefore, using the current helm version in troubleshoot as it is, makes v1 an indirect dependency, still leading to docker v24 incompatibility errors like this At this rate we'd have a mix of v1 and v2 if I bump this up. I'd suggest we discuss this a bit. |
Signed-off-by: Archit Sharma <[email protected]>
Thanks Archit. Status:
|
Signed-off-by: Archit Sharma <[email protected]>
Signed-off-by: Archit Sharma <[email protected]>
Signed-off-by: Archit Sharma <[email protected]>
Signed-off-by: Archit Sharma <[email protected]>
still blocked
|
Bug Description
(Edit: originally thought it was k8s packages driving the need, it's actually containers/image)
The version of oras-go in use (v1) is no longer in active maintenance and is incompatible with new k8s APIs. Need to update, or have oras-project/oras-go#551 fixed with an actual release rather than just a PR.
If we bump docker packages to the latest, oras-go no longer works and
go vet
complains.The solution here is to use the current version of oras, v2.
Expected Behavior
we can update packages cleanly
Steps To Reproduce
Update github.com/containers/image/v5 from 5.25.0 to 5.27.0.
go mod tidy
make vet returns:
Additional Context
The text was updated successfully, but these errors were encountered: