Artix Linux Forum

Artix Linux => System => Topic started by: Hawk on 19 November 2020, 15:23:28

Title: [SOLVED] Unable to run LXD as non root user even after adding to group
Post by: Hawk on 19 November 2020, 15:23:28
when in try to run lxc and lxd as non root user added to lxd group. i get permission error

this does not happen with other applications such as docker and others
Title: Re: Unable to run LXD as non root user even after adding to group
Post by: alium on 19 November 2020, 15:58:08
more info need, put here some output from terminal
Title: Re: Unable to run LXD as non root user even after adding to group
Post by: Hawk on 19 November 2020, 16:18:14
Error: Get "http://unix.socket/1.0": dial unix /var/lib/lxd/unix.socket: connect: permission denied
i get this when i try a normal user. but it works when i a sudo user
Title: Re: Unable to run LXD as non root user even after adding to group
Post by: alium on 19 November 2020, 19:23:56
what say if you run it as user
Code: [Select]
groups
Title: Re: Unable to run LXD as non root user even after adding to group
Post by: Hawk on 19 November 2020, 19:44:09
lxd libvirt docker wheel
Title: Re: Unable to run LXD as non root user even after adding to group
Post by: alium on 19 November 2020, 20:13:33
have you installed and started lxd-openrc/runit/s6 ??

OK i installed lxd and i have same problem...

read please

https://wiki.gentoo.org/wiki/LXD

https://wiki.gentoo.org/wiki/LXD#Cgroups_inside_Containers_with_OpenRC
Title: Re: Unable to run LXD as non root user even after adding to group
Post by: Hawk on 19 November 2020, 21:10:34
thank you. but both of the links were not able to solve the problem. still need  be a sudo user
were you able to solve this . i followed all the steps and rebooted still could not get it working
Title: Re: Unable to run LXD as non root user even after adding to group
Post by: Hawk on 19 November 2020, 21:53:01
i have openrc
Title: Re: Unable to run LXD as non root user even after adding to group
Post by: Hawk on 22 November 2020, 18:55:46
i have a startup script that changes permission of unix.socket
probably not recommended but i had no other option for now