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

minikube: 1.0.1 -> 1.2.0 #65412

Merged
merged 1 commit into from Aug 4, 2019
Merged

Conversation

vdemeester
Copy link
Member

@vdemeester vdemeester commented Jul 26, 2019

Motivation for this change

Bump to latest release (1.2.0) and switch to go modules.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@vdemeester
Copy link
Member Author

@GrahamcOfBorg build minikube

@adisbladis
Copy link
Member

adisbladis commented Jul 26, 2019

Sorry for hijacking this PR, this is not an issue with this PR itself, it's much larger.

We're accepting more and more packages using buildGoModule in nixpkgs even though there is an expressed intent to restrict what we can do with fixed output derivations.
This is at odds and I can't see much reason we keep accepting packages being converted over and making any future efforts to restrict FODs more difficult.

I'd like us to stop accepting new packages that are abusing FODs and start working on gradually removing these abuses.
See NixOS/nix#2270.

cc @Mic92 @kalbasit

@mattmelling
Copy link
Contributor

nix-review fails for me:

builder for '/nix/store/ghpzc56myn409xbx7b22kspbv2xg726b-docker-machine-kvm2-1.2.0.drv' failed with exit code 1; last 10 log lines:
        /build/go/src/k8s.io/client-go/tools/clientcmd/api (from $GOPATH)
  go/src/k8s.io/minikube/pkg/util/kubeconfig.go:33:2: cannot find package "k8s.io/client-go/tools/clientcmd/api/latest" in any of:
        /nix/store/ivsk24l5dsdlyx92mnvkp4075hzpjfpj-go-1.12.7/share/go/src/k8s.io/client-go/tools/clientcmd/api/latest (from $GOROOT)
        /build/go/src/k8s.io/client-go/tools/clientcmd/api/latest (from $GOPATH)
  go/src/k8s.io/minikube/pkg/minikube/constants/constants.go:30:2: cannot find package "k8s.io/client-go/util/homedir" in any of:
        /nix/store/ivsk24l5dsdlyx92mnvkp4075hzpjfpj-go-1.12.7/share/go/src/k8s.io/client-go/util/homedir (from $GOROOT)
        /build/go/src/k8s.io/client-go/util/homedir (from $GOPATH)
  go/src/k8s.io/minikube/pkg/util/kubernetes.go:38:2: cannot find package "k8s.io/kubernetes/cmd/kubeadm/app/constants" in any of:
        /nix/store/ivsk24l5dsdlyx92mnvkp4075hzpjfpj-go-1.12.7/share/go/src/k8s.io/kubernetes/cmd/kubeadm/app/constants (from $GOROOT)
        /build/go/src/k8s.io/kubernetes/cmd/kubeadm/app/constants (from $GOPATH)
builder for '/nix/store/mci9nxq9ccamgw4r8lw7pa72qlf5ysfg-minikube-1.2.0.drv' failed with exit code 1; last 10 log lines:
  k8s.io/minikube/pkg/minikube/logs
  k8s.io/minikube/pkg/minikube/notify
  k8s.io/minikube/pkg/minikube/tunnel
  k8s.io/minikube/third_party/go9p
  k8s.io/minikube/third_party/go9p/ufs
  k8s.io/minikube/cmd/minikube/cmd
  k8s.io/minikube/cmd/minikube
  glibPreInstallPhase
  installing
  mkdir: cannot create directory '/share': Permission denied
cannot build derivation '/nix/store/sr212h8lfpn9l1gv0yn92q32hfr78yw9-env.drv': 2 dependencies couldn't be built

I don't know enough about the particular builder but it seems like $bin isn't being set correctly.

@kalbasit
Copy link
Member

Sorry for hijacking this PR, this is not an issue with this PR itself, it's much larger.

We're accepting more and more packages using buildGoModule in nixpkgs even though there is an expressed intent to restrict what we can do with fixed output derivations.
This is at odds and I can't see much reason we keep accepting packages being converted over and making any future efforts to restrict FODs more difficult.

I'd like us to stop accepting new packages that are abusing FODs and start working on gradually removing these abuses.
See NixOS/nix#2270.

cc @Mic92 @kalbasit

Thanks for the pointer, I have missed this issue. I don't think we should worry about that now. It's an issue today, and won't be resolved for a long while. Until then, we should do business as usual. Whatever the solution will be, it will have to take into account the current packages by either changing buildGoModule itself, or via a script to fix them all -- in which case converting/adding more packages won't matter as much.

@kalbasit
Copy link
Member

@GrahamcOfBorg build minikube

Also switch to go modules.

Signed-off-by: Vincent Demeester <vincent@sbr.pm>
@offlinehacker
Copy link
Contributor

offlinehacker commented Aug 4, 2019

@adisbladis I do not see this being the case, there's a discussion how to solve this issue, but until better solution is found, we rather have a way to have packages updated, as to stop packaging.

PS: and you can also see that many people disagree with proposed restrictions, as there are currently only bad alternatives

@kalbasit
Copy link
Member

kalbasit commented Aug 4, 2019

@GrahamcOfBorg build minikube

@offlinehacker
Copy link
Contributor

Darwin failure is unrelated, seems like clang is failing

@offlinehacker offlinehacker merged commit 0dc218e into NixOS:master Aug 4, 2019
@kalbasit kalbasit mentioned this pull request Aug 4, 2019
10 tasks
@vdemeester vdemeester deleted the update-minikube branch August 5, 2019 09:02
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.

None yet

5 participants