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

Unable to go get #48

Closed
micahyoung opened this issue Oct 10, 2018 · 3 comments
Closed

Unable to go get #48

micahyoung opened this issue Oct 10, 2018 · 3 comments

Comments

@micahyoung
Copy link
Member

Expected behavior:
I can use go get github.com/buildpack/pack to fetch source

Observed behavior:
Failure when running, apparently due to mismatched imported, vendored deps

$ docker run -it golang:1.11.1
root@2b66f88f9793:/go# go get github.com/buildpack/pack
# github.com/buildpack/pack/image
src/github.com/buildpack/pack/image/image.go:28:2: cannot use origImage (type "github.com/buildpack/lifecycle/vendor/github.com/google/go-containerregistry/pkg/v1".Image) as type "github.com/google/go-containerregistry/pkg/v1".Image in return argument:
        "github.com/buildpack/lifecycle/vendor/github.com/google/go-containerregistry/pkg/v1".Image does not implement "github.com/google/go-containerregistry/pkg/v1".Image (wrong type for BlobSet method)
                have BlobSet() (map["github.com/buildpack/lifecycle/vendor/github.com/google/go-containerregistry/pkg/v1".Hash]struct {}, error)
                want BlobSet() (map["github.com/google/go-containerregistry/pkg/v1".Hash]struct {}, error)
@sclevine
Copy link
Member

This project requires Go Modules which can be enabled with GO111MODULE=on. However, this will not make go get work like you describe (see here). Instead of using go get, clone the repo and run go build ..

@micahyoung
Copy link
Member Author

Thanks @sclevine. I realize I should have peeked at the travis.yml too. I was able to get it cross-compiled and now looking forward to trying it out on Windows.

@nebhale
Copy link
Contributor

nebhale commented Oct 15, 2018

Not that this would have been helped by the request in #45.

natalieparellano added a commit that referenced this issue Jul 17, 2024
When creating volume caches, incorporate "pack volume key" to avoid name collisions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants