missing or incomplete nats configuration. #1080
Replies: 1 comment 2 replies
-
My issue was that I had a misconfiguration in the Pod (missing a |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to run OpenCloud in my Homelab on K3s. I've tried the Helm chart but unfortunately it still has a few shortcomings, so instead I tried to build my own small deployment based on the Docker compose example. I'm a bit stuck now and not sure how to proceed. I've taken quite a bit of are to use the relevant bits of configuration from the example, but I must be missing something.
My collaboration container logs:
Checking the opencloud container logs, it seems nats is starting fine:
But then the
storage-system
andocm
services complain about nats, which seems connected to the issue with the companion container:The relevant env vars in the opencloud container are (let me know if I'm missing some):
The
9233
is configured in theService
foropencloud
as well which the companion uses to communicate with nats (MICRO_REGISTRY_ADDRESS: "opencloud:9233"
in the companion container).I'd much appreciate a hint of what could be configured wrong! Thanks
Beta Was this translation helpful? Give feedback.
All reactions