Hi, we are running rancher on a single node docker...
# general
g
Hi, we are running rancher on a single node docker install and we frequently run into this error:
2025/08/06 143013 [FATAL] Internal error occurred: failed calling webhook "rancher.cattle.io.settings.management.cattle.io": failed to call webhook: Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/validation/settings.management.cattle.io?timeout=10s": no endpoints available for service "rancher-webhook"
We can get around it by following the instructions here: https://github.com/rancher/rancher/issues/35068#issuecomment-954457381 We are on rancher version v2.11.1 but this has happened since v2.8.5. One thing to note is that we do stop the rancher docker container frequently for backups by following the instructions in Backing up Rancher Installed with Docker Any ideas how to prevent this from happening?
b
> Any ideas how to prevent this from happening? This might sound sarcastic, but don't take it this way: Don't run rancher on a single node.
not having a single point of failure for things like webhooks is the main reason you want to run clusters in HA.
I'm not sure there's going to be another to do what you want and keep it stable on a single node, but adding more nodes would def help.
g
@bland-article-62755 I hear you, we've been told to avoid a single node especially on Docker and we do plan on migrating to a K8s cluster but haven't had time to make that leap yet.
Do you have any suggestions for a temporary workaround while still on Docker?
b
None that are good. You can script out your fix and run it on a cron.
😅
g
It looks like that workaround I linked to doesn't even work anymore on this version of Rancher since the
kubectl
commands don't output anything.
c
The standalone docker container is not supported and should not be used for anything except lightweight dev/proof-of-concept. I know you're planning on getting off it, but doing so asap is really the only recommendation I have.
👍 1
g
@creamy-pencil-82913 Ok, thanks for the suggestion. I'll try to get to that ASAP.