You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this might be a dupe or at least partial dupe of #73, but it's really crampin' my style, so I'd like to make sure you folks upstream know about it, because I cannot imagine I'm the only one.
My use case is; I'm trying to run an application inside of Kubernetes with a Rabbit broker. However, I need persistence. Since I cannot set the hostname via Kubernetes (reported, as issue 4825 I cannot run Rabbit in the cluster.
Running two nodes on the same host is perfectly possible: change the part before the @. For example, some of our test suites use rabbit@hostname and hare@hostname.
Sorry for my ignorance! I had seen the RABBITMQ_NODENAME variable in the documentation and tried using it, but was not setting up my container correctly.
I think this might be a dupe or at least partial dupe of #73, but it's really crampin' my style, so I'd like to make sure you folks upstream know about it, because I cannot imagine I'm the only one.
My use case is; I'm trying to run an application inside of Kubernetes with a Rabbit broker. However, I need persistence. Since I cannot set the hostname via Kubernetes (reported, as issue 4825 I cannot run Rabbit in the cluster.
For reference: docker-library/rabbitmq#6
The text was updated successfully, but these errors were encountered: