-
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
[Podman v4] minikube delete
does not remove Podman's minikube
network
#13861
Labels
area/networking
networking issues
co/podman-driver
podman driver issues
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/bug
Categorizes issue or PR as related to a bug.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone
Comments
Hi @AkihiroSuda, thanks for reporting your issue with minikube! This is definitely an issue, thanks for bringing it to our attention! |
spowelljr
added
kind/bug
Categorizes issue or PR as related to a bug.
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
area/networking
networking issues
labels
Mar 28, 2022
I'm seeing deletion of all volumes and networks here (with 3.4.2), even if there is no user output.
Maybe the filters got broken again ? |
Maybe a breaking change in v4? |
Yes, the Podman 3.4.4
$ sudo podman network inspect minikube
[
{
"args": {
"podman_labels": {
"created_by.minikube.sigs.k8s.io": "true"
}
},
"cniVersion": "0.4.0",
"name": "minikube",
"plugins": [
{
"bridge": "cni-podman2",
"hairpinMode": true,
"ipMasq": true,
"ipam": {
"ranges": [
[
{
"gateway": "192.168.49.1",
"subnet": "192.168.49.0/24"
}
]
],
"routes": [
{
"dst": "0.0.0.0/0"
}
],
"type": "host-local"
},
"isGateway": true,
"type": "bridge"
},
{
"capabilities": {
"portMappings": true
},
"type": "portmap"
},
{
"backend": "",
"type": "firewall"
},
{
"type": "tuning"
},
{
"capabilities": {
"aliases": true
},
"domainName": "dns.podman",
"type": "dnsname"
}
]
}
]
$ sudo podman network inspect minikube --format '{{range .plugins}}{{if eq .type "bridge"}}{{(index (index .ipam.ranges 0) 0).subnet}},{{(index (index .ipam.ranges 0) 0).gateway}}{{end}}{{end}}'
192.168.49.0/24,192.168.49.1 Podman 4.0.2
$ sudo podman network inspect minikube
[
{
"name": "minikube",
"id": "e0fa249ecbb298366798da5840753b985ebcc6b011a28d037d74e4a925ef52b1",
"driver": "bridge",
"network_interface": "podman1",
"created": "2022-03-30T05:28:49.494426782Z",
"subnets": [
{
"subnet": "192.168.49.0/24",
"gateway": "192.168.49.1"
}
],
"ipv6_enabled": false,
"internal": false,
"dns_enabled": true,
"labels": {
"created_by.minikube.sigs.k8s.io": "true"
},
"ipam_options": {
"driver": "host-local"
}
}
]
$ sudo podman network inspect minikube --format '{{range .plugins}}{{if eq .type "bridge"}}{{(index (index .ipam.ranges 0) 0).subnet}},{{(index (index .ipam.ranges 0) 0).gateway}}{{end}}{{end}}'
ERRO[0000] Printing inspect output: template: network inspect:1:19: executing "network inspect" at <.plugins>: can't evaluate field plugins in type interface {} |
AkihiroSuda
changed the title
[Podman v4] Mar 30, 2022
minikube delete
does not remove Podman's minikube
networkminikube delete
does not remove Podman's minikube
network
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/networking
networking issues
co/podman-driver
podman driver issues
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/bug
Categorizes issue or PR as related to a bug.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
What Happened?
minikube delete
does not remove Podman'sminikube
network.Host: minikube 1.25.2, Podman 4.0.2, Ubuntu 21.10.
Attach the log file
Operating System
Ubuntu
Driver
Podman
The text was updated successfully, but these errors were encountered: