In short, any container that is not included in OmniStream is a custom container and can potentially be added to your configuration. This tutorial will talk you through the basics... though it's not entirely for the faint of heart.

First, a small disclaimer: we do not officially support every single container you wish to add. We will certainly try to help if you are stuck, but the content and conversion of the containers is entirely your own responsibility.

That said, if you have a custom container that you want to convert, a good place to start is the components tree in the Omni GitHub pages. Pick one that is closest to the one you want to create, and adapt it to work with OmniStream.

In this tutorial, we'll use Radarr4K as an easy example to follow along with. In this case, of course the closest container is Radarr itself. Use your favorite editor to adapt the Radarr yaml file to Radarr4k.

All OmniStream's components are located in ~/OmniStream/components. Navigate to that folder and add your yaml file there. Make absolutely sure that you start your file name with a number in the 800-899 range. In our case, since it's the first custom container, we named our file 801-radarr4k.yaml.

Type omni components to list your components. Scroll all the way to the bottom and you'll notice your newly added file is listed. Activate it by placing an asterisk in the box, and clicking OK.

Finally, type omni up to create your DNS entry (if using Cloudflare) and activate your new container.