-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add --network flag to select docker network to run with docker driver #9538
Conversation
/ok-to-test |
kvm2 Driver |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there should be added a warnning if using Bridge network, minikube will not have static IP.
since bridge network is not controlable by non-docker itsef
kvm2 Driver Times for Minikube (PR 9538): 62.5s 56.8s 58.1s Averages Time Per Log
docker Driver Times for Minikube (PR 9538): 28.3s 29.6s 28.2s Averages Time Per Log
|
kvm2 Driver Times for Minikube (PR 9538): 61.2s 59.7s 60.9s Averages Time Per Log
docker Driver Times for Minikube (PR 9538): 29.0s 28.8s 28.8s Averages Time Per Log
|
@medyagh now that we have the MTU fix in, do you think it's worth it to add this flag? I'm worried it won't be particularly useful and we're just adding another flag option to |
kvm2 Driver Times for Minikube (PR 9538): 62.6s 61.1s 60.0s Averages Time Per Log
docker Driver Times for Minikube (PR 9538): 29.3s 28.7s 29.8s Averages Time Per Log
|
Travis tests have failedHey @priyawadhwa, 1st Buildmake test
TravisBuddy Request Identifier: 91cddcc0-17d6-11eb-bc4d-2726ba7bdf50 |
kvm2 Driver Times for Minikube (PR 9538): 59.4s 62.4s 59.4s Averages Time Per Log
docker Driver Times for Minikube (PR 9538): 29.7s 31.4s 28.0s Averages Time Per Log
|
I think this flag would still be useful, particularly for cases where Docker is running remotely. I had wanted to recommend this flag to a WSL2 user running into networking problems today :( |
kvm2 Driver Times for Minikube (PR 9538): 63.2s 61.2s 63.1s Averages Time Per Log
docker Driver Times for Minikube (PR 9538): 28.5s 29.2s 29.5s Averages Time Per Log
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
plz check failed test
use_default_bridge_network
" is supported on user defined networks only."
we can't specify ip on default netwokr
@priyawadhwa - do you mind resolving the conflict and looking at the failing test @medyagh mentioned? |
kvm2 Driver Times for Minikube (PR 9538): 58.9s 58.6s 58.6s Averages Time Per Log
docker Driver Times for Minikube (PR 9538): 24.7s 23.1s 23.2s Averages Time Per Log
|
/retest-this-please |
kvm2 Driver Times for Minikube (PR 9538): 59.9s 61.6s 59.7s Averages Time Per Log
docker Driver Times for Minikube (PR 9538): 25.3s 25.2s 24.1s Averages Time Per Log
|
kvm2 Driver Times for Minikube (PR 9538): 58.6s 61.7s 62.9s Averages Time Per Log
docker Driver Times for Minikube (PR 9538): 24.4s 25.0s 25.8s Averages Time Per Log
|
/ok-to-test |
cmd/minikube/cmd/start_flags.go
Outdated
@@ -293,12 +295,17 @@ func generateClusterConfig(cmd *cobra.Command, existing *config.ClusterConfig, k | |||
out.WarningT("With --network-plugin=cni, you will need to provide your own CNI. See --cni flag as a user-friendly alternative") | |||
} | |||
|
|||
if !driver.IsKIC(drvName) && viper.GetString(network) != "" { | |||
out.WarningT("--network flag is only valid with the docker driver, it will be ignored") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- podman driver here
kvm2 Driver Times for Minikube (PR 9538): 60.1s 59.7s 61.5s Averages Time Per Log
docker Driver Times for Minikube (PR 9538): 25.9s 26.2s 25.6s Averages Time Per Log
|
thank you for this great PR @priyawadhwa |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: medyagh, priyawadhwa, tstromberg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Users can now select the network they want to run the docker driver with. If left empty, we will default to creating a new network so that static IP changes can be maintained. Users can go back to using default network by running: