Running docker containers after terraform destroy

[koboltmarky]

Hi there,

i created a rancher2_cluster with the following terraform file.

Creating the cluster works like expected, but when i destroy the cluster with terraform destroy, there are still runnning docker containers on the nodes.

For example:

docker ps --format "table {{.ID}}\t{{.Command}}\t{{.Names}}"
CONTAINER ID        COMMAND                  NAMES
404b8d1bb84d        "/usr/bin/dumb-init …"   k8s_nginx-ingress-controller_nginx-ingress-controller-mcbtt_ingress-nginx_0ed3b4da-d0c6-46db-9ff7-da807f9173bb_15
6b51f817d37b        "/opt/bin/flanneld -…"   k8s_kube-flannel_canal-qgrv5_kube-system_8d2b9dd7-d70a-415e-af20-b7ed4dc937cb_1
87cfbec9a804        "start_runit"            k8s_calico-node_canal-qgrv5_kube-system_8d2b9dd7-d70a-415e-af20-b7ed4dc937cb_1
acbf1c7c16b0        "prometheus-auth --p…"   k8s_prometheus-agent_prometheus-cluster-monitoring-0_cattle-prometheus_87f7aaf0-700e-45bb-947f-686023f118a8_1
a6e90e1b5ea7        "/bin/sh -c 'cp /ngi…"   k8s_prometheus-proxy_prometheus-cluster-monitoring-0_cattle-prometheus_87f7aaf0-700e-45bb-947f-686023f118a8_1
c3e7073d66ca        "/configmap-reload -…"   k8s_rules-configmap-reloader_prometheus-cluster-monitoring-0_cattle-prometheus_87f7aaf0-700e-45bb-947f-686023f118a8_1
e22df18465eb        "/bin/prometheus-con…"   k8s_prometheus-config-reloader_prometheus-cluster-monitoring-0_cattle-prometheus_87f7aaf0-700e-45bb-947f-686023f118a8_1
f38cc6292f64        "/bin/prometheus --w…"   k8s_prometheus_prometheus-cluster-monitoring-0_cattle-prometheus_87f7aaf0-700e-45bb-947f-686023f118a8_1
2f10828a3a1b        "/bin/operator --kub…"   k8s_prometheus-operator_prometheus-operator-monitoring-operator-5bc4cdb76c-v22fm_cattle-prometheus_626a1088-9aec-4e68-b34b-85934933224b_1
23622ce07b51        "/pause"                 k8s_POD_prometheus-cluster-monitoring-0_cattle-prometheus_87f7aaf0-700e-45bb-947f-686023f118a8_1
97ff5817b1e8        "/pause"                 k8s_POD_prometheus-operator-monitoring-operator-5bc4cdb76c-v22fm_cattle-prometheus_626a1088-9aec-4e68-b34b-85934933224b_1
975c5ba1c882        "/bin/node_exporter …"   k8s_exporter-node_exporter-node-cluster-monitoring-w4f7q_cattle-prometheus_8d728138-02e6-4415-bb17-8db690e4d86e_1
fb42225fb5a4        "/pause"                 k8s_POD_exporter-node-cluster-monitoring-w4f7q_cattle-prometheus_8d728138-02e6-4415-bb17-8db690e4d86e_1
8d4755aa10d7        "/pause"                 k8s_POD_canal-qgrv5_kube-system_8d2b9dd7-d70a-415e-af20-b7ed4dc937cb_1
498c3ce3a674        "run.sh"                 k8s_agent_cattle-node-agent-fcx46_cattle-system_dc101f0f-d656-4097-9d99-fec6d6baacbb_1
b34be4880514        "/pause"                 k8s_POD_nginx-ingress-controller-mcbtt_ingress-nginx_0ed3b4da-d0c6-46db-9ff7-da807f9173bb_1
d741c4a7c908        "/pause"                 k8s_POD_cattle-node-agent-fcx46_cattle-system_dc101f0f-d656-4097-9d99-fec6d6baacbb_1

Terraform Version

Terraform v0.12.24

• provider.helm v1.2.1
• provider.kubernetes v1.10.0
• provider.local v1.4.0
• provider.null v2.1.2
• provider.rancher2 v1.8.3
• provider.rke v1.0.0

Affected Resource(s)

• rancher2_cluster

[mcanevet]

Well, this provider is about Rancher1 (up to v1.6.x). You should open an issue on Rancher2's provider repository : https://github.com/rancher/terraform-provider-rancher2