Describe the bug
as mentioned here: https://github.com/rancher/k3s#uninstalling-server
if I'm running the k3s uninstall script under /usr/local/bin/k3s-uninstall.sh . The script is not removing all the k8s containers
To Reproduce
1) install k3s using --docker option
2) deploy some services
3) run /usr/local/bin/k3s-uninstall.sh
4) list all dockers: docker ps
Expected behavior
the script /usr/local/bin/k3s-uninstall.sh should clear also all the k8s containers
Screenshots
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
cc2b923a962b rancher/rancher-agent "run.sh" About an hour ago Up About an hour k8s_agent_cattle-node-agent-972w6_cattle-system_5bb67096-a262-11e9-afda-7085c277ab91_0
6e60376c03c0 rancher/rancher-agent "run.sh" About an hour ago Up About an hour k8s_cluster-register_cattle-cluster-agent-c549645f-hjc7q_cattle-system_599631c9-a262-11e9-afda-7085c277ab91_0
dd81bbca526e k8s.gcr.io/pause:3.1 "/pause" About an hour ago Up About an hour k8s_POD_cattle-node-agent-972w6_cattle-system_5bb67096-a262-11e9-afda-7085c277ab91_0
6331f16e7196 k8s.gcr.io/pause:3.1 "/pause" About an hour ago Up About an hour k8s_POD_cattle-cluster-agent-c549645f-hjc7q_cattle-system_599631c9-a262-11e9-afda-7085c277ab91_0
122f0beac9de k8s.gcr.io/pause:3.1 "/pause" About an hour ago Up About an hour k8s_POD_rancher-855654f77b-zstxn_cattle-system_320fe9b2-a262-11e9-afda-7085c277ab91_0
074cc299026f 4a065d8dfa58 "entry" About an hour ago Up About an hour k8s_lb-port-80_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_1
05c0fc0f6f55 4a065d8dfa58 "entry" About an hour ago Up About an hour k8s_lb-port-9443_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_0
e18c917dad07 4a065d8dfa58 "entry" About an hour ago Up About an hour k8s_lb-port-8081_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_0
b86a74146d5f 4a065d8dfa58 "entry" About an hour ago Up About an hour k8s_lb-port-7443_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_0
087d3e106421 4a065d8dfa58 "entry" About an hour ago Up About an hour k8s_lb-port-5672_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_0
fb413ccf6150 4a065d8dfa58 "entry" About an hour ago Up About an hour k8s_lb-port-5671_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_0
1cf2e6524b3d 4a065d8dfa58 "entry" About an hour ago Up About an hour k8s_lb-port-50051_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_0
399c799f6371 4a065d8dfa58 "entry" About an hour ago Up About an hour k8s_lb-port-3000_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_0
d65db757c9d1 4a065d8dfa58 "entry" About an hour ago Up About an hour k8s_lb-port-27017_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_0
9bd80af9444b 4a065d8dfa58 "entry" About an hour ago Up About an hour k8s_lb-port-2000_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_0
16d761848774 4a065d8dfa58 "entry" About an hour ago Up About an hour k8s_lb-port-1935_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_0
d3bfd6b2e5c2 4a065d8dfa58 "entry" About an hour ago Up About an hour k8s_lb-port-16180_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_0
d35f54c27ec7 4a065d8dfa58 "entry" About an hour ago Up About an hour k8s_lb-port-15671_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_0
500421d852d5 4a065d8dfa58 "entry" About an hour ago Up About an hour k8s_lb-port-1080_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_0
4d1208370bba 4a065d8dfa58 "entry" About an hour ago Up About an hour k8s_lb-port-443_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_0
6261b9cd7989 k8s.gcr.io/defaultbackend-amd64 "/server" About an hour ago Up About an hour k8s_nginx-ingress-default-backend_ingress-nginx-nginx-ingress-default-backend-7648784fb6-9kw84_ingress-nginx_ed126302-a261-11e9-afda-7085c277ab91_0
0b59db060c42 quay.io/kubernetes-ingress-controller/nginx-ingress-controller "/usr/bin/dumb-init …" About an hour ago Up About an hour k8s_nginx-ingress-controller_ingress-nginx-nginx-ingress-controller-898469db6-gf2z4_ingress-nginx_ed1223f3-a261-11e9-afda-7085c277ab91_0
2a148e11ca11 k8s.gcr.io/pause:3.1 "/pause" About an hour ago Up About an hour k8s_POD_svclb-ingress-nginx-nginx-ingress-controller-lhqcn_ingress-nginx_ed1212f2-a261-11e9-afda-7085c277ab91_0
67b16bd8fa88 k8s.gcr.io/pause:3.1 "/pause" About an hour ago Up About an hour k8s_POD_ingress-nginx-nginx-ingress-default-backend-7648784fb6-9kw84_ingress-nginx_ed126302-a261-11e9-afda-7085c277ab91_0
49825e73f865 k8s.gcr.io/pause:3.1 "/pause" About an hour ago Up About an hour k8s_POD_ingress-nginx-nginx-ingress-controller-898469db6-gf2z4_ingress-nginx_ed1223f3-a261-11e9-afda-7085c277ab91_0
1a8f34604544 k8s.gcr.io/pause:3.1 "/pause" About an hour ago Up About an hour k8s_POD_cert-manager-5d669ffbd8-7xz7w_cert-manager_ecf33883-a261-11e9-afda-7085c277ab91_0
68476ed4e23e k8s.gcr.io/pause:3.1 "/pause" About an hour ago Up About an hour k8s_POD_cert-manager-cainjector-79b7fc64f-tpb5z_cert-manager_ecf2da41-a261-11e9-afda-7085c277ab91_0
121b74f4e804 coredns/coredns "/coredns -conf /etc…" About an hour ago Up About an hour k8s_coredns_coredns-695688789-d77sm_kube-system_dc7376d6-a261-11e9-afda-7085c277ab91_0
1e1e94551134 k8s.gcr.io/pause:3.1 "/pause" About an hour ago Up About an hour k8s_POD_local-path-provisioner-69fc9568b9-btfb5_local-path-storage_dc740271-a261-11e9-afda-7085c277ab91_0
f5d03d7ede2f k8s.gcr.io/pause:3.1 "/pause" About an hour ago Up About an hour k8s_POD_coredns-695688789-d77sm_kube-system_dc7376d6-a261-11e9-afda-7085c277ab91_0
it should be noted that this problem occurs when k3s is run with the --docker option.
Any update on this issue.?
@saurav-k are you still seeing this issue?
@brandond Which release fixed this issue .? I am still facing it.
k3s-killall.sh only kills containerd containers. If you are using docker, you should simply stop docker after stopping/uninstalling k3s.
Most helpful comment
it should be noted that this problem occurs when k3s is run with the --docker option.