-
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
Support rootless Podman driver ( minikube start --driver=podman --rootless --container-runtime=(cri-o|containerd)
)
#12901
Conversation
Can one of the admins verify this patch? |
6482ea9
to
40e5461
Compare
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.
thank you for this PR, I think we just need to delete where we set the env and let "viper" lib take care of setting the env
@@ -135,6 +135,10 @@ func platform() string { | |||
|
|||
// runStart handles the executes the flow of "minikube start" | |||
func runStart(cmd *cobra.Command, args []string) { | |||
if cmd.Flag(rootless).Changed { | |||
// env is internally used by kic runner | |||
os.Setenv(constants.MinikubeRootlessEnv, strconv.FormatBool(viper.GetBool(rootless))) |
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.
don't think we need to set env I believe viper lib already sets the env from the flags
check the other usages of Env as flag
MinikubeForceSystemdEnv = "MINIKUBE_FORCE_SYSTEMD"
so I believe we could delete this code
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.
viper seems to map $MINIKUBE_ROOTLESS
to --rootless
automatically, but it does not do vice versa.
Updated the comment lines to clarify that.
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.
makes sense, thank you for the clarification
40e5461
to
65f4a51
Compare
minikube start --driver=podman --rootless --container-runtime=containerd
)minikube start --driver=podman --rootless --container-runtime=(cri-o|containerd)
)
65f4a51
to
7eba4c5
Compare
@afbjorklund Could you take a look |
7eba4c5
to
e9f6858
Compare
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.
thank you for this PR
/ok-to-test |
kvm2 driver with docker runtime
Times for minikube start: 49.7s 44.1s 44.6s 46.1s 44.4s Times for minikube ingress: 29.0s 30.1s 29.0s 29.1s 29.1s docker driver with docker runtime |
These are the flake rates of all failed tests.
To see the flake rates of all tests by environment, click here. |
/ok-to-test |
kvm2 driver with docker runtime
Times for minikube start: 51.8s 45.0s 44.9s 44.8s 45.9s Times for minikube ingress: 29.6s 29.6s 29.6s 30.6s 31.6s docker driver with docker runtime
Times for minikube start: 27.4s 26.9s 26.8s 26.2s 26.8s Times for minikube ingress: 22.9s 22.9s 23.4s 22.9s 22.9s docker driver with containerd runtime
Times for minikube start: 44.4s 41.9s 41.6s 41.7s 42.4s Times for minikube ingress: 64.9s 37.4s 36.9s 33.4s 37.4s |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
Is there any remaining task that I have to do? |
Rebased |
678a94f
to
58d33b5
Compare
rebased |
kvm2 driver with docker runtime
Times for minikube start: 49.8s 50.9s 52.0s 52.6s 51.2s Times for minikube ingress: 28.5s 29.5s 29.0s 29.0s 29.1s docker driver with docker runtime
Times for minikube ingress: 22.9s 22.9s 22.9s 21.9s 20.9s Times for minikube start: 26.9s 25.7s 25.0s 25.6s 25.6s docker driver with containerd runtime
Times for minikube start: 31.0s 45.5s 44.5s 45.2s 41.7s Times for minikube ingress: 23.4s 19.4s 18.9s 18.9s 22.9s |
These are the flake rates of all failed tests.
To see the flake rates of all tests by environment, click here. |
@medyagh @afbjorklund Is there any remaining task to get this merged? 🙏 |
58d33b5
to
633f303
Compare
kvm2 driver with docker runtime
Times for minikube start: 53.5s 51.5s 52.4s 53.2s 53.4s Times for minikube (PR 12901) ingress: 25.1s 30.5s 28.5s 25.5s 29.6s docker driver with docker runtime
Times for minikube (PR 12901) start: 25.2s 25.8s 26.3s 27.2s 25.8s Times for minikube ingress: 21.9s 21.9s 22.4s 23.0s 22.9s docker driver with containerd runtime
Times for minikube start: 30.4s 45.4s 40.6s 41.2s 41.5s Times for minikube ingress: 23.4s 18.9s 33.4s 22.9s 22.9s |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
/ok-to-test |
kvm2 driver with docker runtime
Times for minikube start: 53.7s 52.7s 52.8s 53.8s 53.7s Times for minikube (PR 12901) ingress: 29.1s 26.1s 26.1s 29.6s 30.6s docker driver with docker runtime
Times for minikube start: 30.9s 26.8s 26.4s 27.0s 26.8s Times for minikube ingress: 21.9s 23.4s 23.9s 22.5s 22.5s docker driver with containerd runtime
Times for minikube start: 35.2s 45.8s 45.5s 42.0s 42.9s Times for minikube ingress: 30.0s 20.0s 20.0s 24.0s 33.4s |
These are the flake rates of all failed tests.
Too many tests failed - See test logs for more details. To see the flake rates of all tests by environment, click here. |
CI failures are unrelated https://storage.googleapis.com/minikube-builds/logs/12901/22700/Docker_macOS.html#fail_TestSkaffold
|
Usage: `minikube start --driver=podman --rootless --container-runtime=(cri-o|containerd)` Tested on Podman 3.4.1, Ubuntu 21.10. Needs cgroup v2 (as in Rootless Docker): https://rootlesscontaine.rs/getting-started/common/cgroup2/ See also `site/content/en/docs/drivers/includes/podman_usage.inc` Fix issue 8719 Fix issue 12460 Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
633f303
to
2bbf53a
Compare
Rebased |
kvm2 driver with docker runtime
Times for minikube ingress: 28.5s 29.1s 25.1s 29.1s 30.0s Times for minikube start: 53.3s 55.2s 52.5s 54.6s 52.5s docker driver with docker runtime
Times for minikube start: 30.3s 25.9s 26.9s 25.8s 26.6s Times for minikube ingress: 23.9s 21.9s 21.9s 24.0s 23.4s docker driver with containerd runtime
Times for minikube start: 30.8s 41.2s 40.7s 40.4s 42.6s Times for minikube ingress: 23.4s 23.4s 23.4s 53.4s 23.4s |
These are the flake rates of all failed tests.
To see the flake rates of all tests by environment, click here. |
@AkihiroSuda: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Usage:
minikube start --driver=podman --rootless --container-runtime=(cri-o|containerd)
Tested on Podman 3.4.1, Ubuntu 21.10.
Needs cgroup v2 (as in Rootless Docker): https://rootlesscontaine.rs/getting-started/common/cgroup2/
See also
site/content/en/docs/drivers/includes/podman_usage.inc
Fix #8719
Fix #12460
Follow-up to #12359 (Rootless Docker driver)