So, from what I've seen, it's possible to run a dbus inside a container.
You need to start it from your entrypoint script. I've done this in
the past, but not for several years.
That said, this may be a legit reason to add multiple bus keys. I can
see wanting to control them from outside, b
I am running ganesha inside docker containers. I have tried to run dbus
inside docker, but that fails because system_bus_socket does not exist.
This is the actual problem.
To solve this, I am using the host dbus server from containers by mounting
the host system_bus_socket inside the containers. S
On 10/03/2017 02:31 AM, sriram patil wrote:
Hi,
AFAIK we can run only single instance of nfs-ganesha on a given
machine which supports dbus signals. Running with different ports, nfs
ganesha service comes up, but the dbus signals work only for the first
(primary) instance. We cannot interact wit
On 10/03/2017 02:31 AM, sriram patil wrote:
Hi,
AFAIK we can run only single instance of nfs-ganesha on a given
machine which supports dbus signals. Running with different ports, nfs
ganesha service comes up, but the dbus signals work only for the first
(primary) instance. We cannot interact wit
Hi,
AFAIK we can run only single instance of nfs-ganesha on a given
machine which supports dbus signals. Running with different ports, nfs
ganesha service comes up, but the dbus signals work only for the first
(primary) instance. We cannot interact with the ganesha instances
(other than primary) t
