diff --git a/docs/software/container-engine/resource-hook.md b/docs/software/container-engine/resource-hook.md
index 72707731..bce9cc8d 100644
--- a/docs/software/container-engine/resource-hook.md
+++ b/docs/software/container-engine/resource-hook.md
@@ -169,6 +169,36 @@ The hook is activated by setting the `com.hooks.cxi.enabled` annotation, which
     4194304             23925.61
     ```
 
+!!! tip "How to check the CXI provider works inside a container"
+
+    You might want to check if the CXI provider works inside a container,
+    i.e. that the CXI hook has been correctly applied.
+
+    You can check if the CXI provider is working using `fi_info`,
+    usually available alongside your `libfabric` installation,
+    within the container:
+
+    ```bash
+    fi_info -p cxi
+    ```
+
+    ??? example "CXI provider is working"
+        ```console
+        $ fi_info -p cxi
+        provider: cxi
+            fabric: cxi
+            domain: cxi0
+            version: 0.1
+            type: FI_EP_RDM
+            protocol: FI_PROTO_CXI
+        ```
+
+    ??? example "CXI provider not working"
+        ```console
+        $ fi_info -p cxi
+        fi_getinfo: -61 (No data available)
+        ```
+
 [](){#ref-ce-aws-ofi-hook}
 ### AWS OFI NCCL hook