How to let user defined in a container to access dbus systembus

[Srinadh Penugonda]

This is what my device is running
root at sonic:~# uname -aLinux sonic 4.19.0-9-2-amd64 #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 GNU/Linux
root at sonic:~#



~~  Thanks, Srinadh

    On Tuesday, December 14, 2021, 01:50:37 PM PST, Daniel Walsh <dwalsh at redhat.com> wrote:  
 
  On 12/14/21 13:04, Srinadh Penugonda wrote:
  
 
  Yes, I did add the mount point for .mk file of the container.    My bad, missed mentioning it my previous email. 
    
  It wasnt there before but even after adding the mount point, it didnt make any difference in the error that see.  
  
    root at sonic:/var/run# ls -F dbus/  frr/  frrcfgd_client_conn_completed  lock/  redis/  redis-chassis/  supervisord.pid  supervisor.sock=  utmp  
     root at 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 at sonic:/var/run/dbus#  
      Is it being blocked by SELinux.  SELinux would definitely not allow this access in a Podman container.
 
   
  
    ~~  Thanks, Srinadh
  
  
     
      On Tuesday, December 14, 2021, 04:08:48 AM PST, Thiago Macieira <thiago at kde.org> wrote:  
  
   On Sunday, 12 December 2021 00:32:13 -03 Srinadh Penugonda wrote:
 > When these processes trying to use dbus, they are not able to get the dbus
 > conn 40        static DBus::Connection conn =
 > DBus::Connection::SystemBus();
 
 DId you bind-mount the system bus socket into the identical path inside the 
 container? 
 
 -- 
 Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel DPG Cloud Engineering 
 
 
 
      
 

 
   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dbus/attachments/20211214/74166dbc/attachment.htm>