# Container Management

![You should see these containers deployed.](/files/CS7UVCiTTfcgo1VFXiDW)

Now that these containers have been deployed, there are a few things to remember.&#x20;

When you created the 'opencti' stack (or whatever you called it), it'll create a default network (opencti\_default). This defines an internal IP range used by docker containers assigned to that network. DHCP is used by default, so you need to remember that if you're going to refer to your OpenCTI host by hostname and not IP address, you need to ensure your DNS settings are configured correctly so the hostname will resolve. That's outside the scope of this guide. If you want to follow along with this guide, just be sure to set a static IP address for your OpenCTI container.

To set a static IP;\
Portainer > Containers > opencti\_opencti\_1 > duplicate/edit > network > set a static IP (which can be communicated with from the other containers on that network)

![](/files/l3IZwy1gVHRM0wUdV72T)

In the above example, the OpenCTI container's IP address is **172.18.0.8**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.iblue.team/opencti/container-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
