# Uninstalling Portworx on air gapped environment such as ICP/CP4data

**URL:** <https://forums.portworx.com/t/uninstalling-portworx-on-air-gapped-environment-such-as-icp-cp4data/252>\
**Category:** Portworx on Kubernetes\
**Created:** [November 7, 2019, 10:31pm UTC](https://forums.portworx.com/t/uninstalling-portworx-on-air-gapped-environment-such-as-icp-cp4data/252 "2019-11-07T22:31:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Luay\_Alem](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/luay_alem/32/58_2.png) [@Luay\_Alem](https://forums.portworx.com/u/Luay_Alem)\
**Post date:** [November 7, 2019, 10:31pm UTC](https://forums.portworx.com/t/uninstalling-portworx-on-air-gapped-environment-such-as-icp-cp4data/252/1 "2019-11-07T22:31:52Z")

</div>

When wiping Portworx in air gapped environment using this documented procedure [https://docs.portworx.com/portworx-install-with-kubernetes/operate-and-maintain-on-kubernetes/uninstall/px-wipe-airgapped/](https://docs.portworx.com/portworx-install-with-kubernetes/operate-and-maintain-on-kubernetes/uninstall/px-wipe-airgapped/) you may run to an issue pulling talisman image which would cause the uninstall to not perform properly. The issue will be addressed in future release of the wiper script. In the meanwhile to work around the issue, the px-node-wiper is a daemonset, so after the wiper script starts up edit the px-node-wiper daemonset `kubectl -n kube-system edit ds px-node-wiper` and add your imagePullSecret under spec:

```auto
     imagePullSecrets:
       - name: "infra-registry-key"

```

where `infra-registry-key` is the name of the registry secret that you created in K8s.