Clarification on Loading Custom Carrier Extensions in Docker & Updating Plugin Docs

[jacobshilitz]

Hi,

I really like the new plugin system introduced in Karrio preview 2025.5rc1.
I’d appreciate it if you could explain in more detail how I can load my own carrier extension into a pre-built Docker image.

I’ve read the README, but it would be great if the official web documentation could also be updated to cover the new plugin structure for easier reference.

I also noticed that the folder structure still follows the pattern modules/connectors/fedex/.... I’m wondering why we keep this structure, or if it’s still necessary under the new plugin system?

Another thing I noticed: the plugins still seem to be installed via pip. I’m a bit confused because I thought the new plugin system would automatically load them via discovery — or perhaps the migration to the new system isn’t fully complete yet?

Thanks!

[danh91]

Hi @jacobshilitz ,

Your assumptions are correct. The plugin system will allow you to just drop plugins like carrier integrations into a folder, and it will get picked up by karrio on start. And pip installation will not be necessary.

Regarding FedEx, we are indeed keeping backward compatibility with the old carrier integration plugin syntax.

I will update the docs with instructions and deployment examples because it is possible to load it even with a docker container by mounting a plugin directory

karrio/docker/api/Dockerfile

Line 41 in ed72e3f

ENV KARRIO_PLUGINS=/karrio/plugins

I will update the docs and notify you.