Skip to content
Snippets Groups Projects
  • Maciek Borzecki's avatar
    576f7cf4
    cmd/incus-user: keep track of socket path used to connect to the server · 576f7cf4
    Maciek Borzecki authored
    
     The logic used to figure out the correct Unix socket path for access to
     the demon in `client.ConnectIncusUnix()` was fixed in in
     d8b78d50 to account for use of
     /run/incus/unix.socket as an alternative socket location. However, the
     proxying code of incus-user was not updated when the fix was
     introduced. As a result, even if initial connection to the server and
     the configuration queries were successful, the actual attempt to proxy
     a client request would fail while trying to connect to
     /var/lib/incus/unix.socket regardless of prior findings.
    
    Signed-off-by: default avatarMaciek Borzecki <maciek.borzecki@gmail.com>
    576f7cf4
    History
    cmd/incus-user: keep track of socket path used to connect to the server
    Maciek Borzecki authored
    
     The logic used to figure out the correct Unix socket path for access to
     the demon in `client.ConnectIncusUnix()` was fixed in in
     d8b78d50 to account for use of
     /run/incus/unix.socket as an alternative socket location. However, the
     proxying code of incus-user was not updated when the fix was
     introduced. As a result, even if initial connection to the server and
     the configuration queries were successful, the actual attempt to proxy
     a client request would fail while trying to connect to
     /var/lib/incus/unix.socket regardless of prior findings.
    
    Signed-off-by: default avatarMaciek Borzecki <maciek.borzecki@gmail.com>