I'm not sure whether I'm even supposed to be starting dbus-daemon inside docker. If i add my nf to /etc/dbus-1/session.d/ in container and override unix:path=/run/user/1000/bus I get the message 'Failed to start message bus: Failed to bind socket "/run/user/1000/bus": Address already in use' run/user/1000/bus is visible from within the container but when the container is started it prints the address unix:abstract=/tmp/dbus-iXrYzptYOX,guid=78a790f0f6a4387a39ac3d505da478a3 and my apps cannot communicate. run/user/1000/bus is the value of my DBUS_SESSION_BUS_ADDRESS variable.Īnd i create container with docker create -mount type=bind,source=/run/user/1000/bus,target=/run/user/1000/bus mycontainer Here's my Dockerfile:ĮNV DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/busĮNTRYPOINT Now I want to move slave app to docker container and I'm having problem sharing d-bus session between host and container. My apps work as expected when being run on the same host. I'm creating two apps, master and slave, which communicate over d-bus.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |