Re: How to let user defined in a container to access dbus systembus
Thiago Macieira <[email protected]>
| Newsgroups | gmane.comp.freedesktop.dbus |
|---|---|
| Message-ID | <1656885.IsgmFpQBkz@tjmaciei-mobl5> |
On Tuesday, 14 December 2021 18:50:16 -03 Daniel Walsh wrote: > > root@sonic:/var/run/dbus# ls -al > > total 4 > > drwxr-xr-x 2 root root 80 Dec 9 19:02 . > > drwxr-xr-x 1 root root 4096 Dec 9 19:03 .. > > srwxrw-rw- 1 root root 0 Dec 9 19:02 histmem.socket > > srw-rw-rw- 1 root root 0 Dec 9 19:02 system_bus_socket > > root@sonic:/var/run/dbus# > > Is it being blocked by SELinux. SELinux would definitely not allow this > access in a Podman container. In any case, the problem is no longer a D-Bus one. It's a matter of getting the socket in the right place, with the right permissions, in the container.