I use Artix, and I'm trying removing elogind, installing seatd but not using dbus, that made running docker images through vagrant not possible:
Stderr: docker: Error response from daemon: failed to create endpoint <...>_1740448731 on network bridge: failed to add the host (veth8af48a7) <=> sandbox (veth907cd9c) pair interfaces: operation not supported.
As the issue is about privileges, I was wondering if it's about seatd, which is the one granting accesses.
BTW, I need to go back to use dbus since I can not share screen through xdg-desktop-portal, perhaps there's dbus communication happening underneath, but I thought it was done rather through sockets. At any rate, as a thing about privileges, I doubt dbus has anything to do with it.
On Artix, the seatd version is 0.9.1, and if you're condering I'm using dinit, version 0.19.3.
So again, is it not possible to run docker images with seatd, my current groups:
% groups
scanner users libvirt seat docker adbusers video storage lp kvm input disk optical audio <my_user_name> network
Before I didn't have "network" but it made no difference adding it...
Thanks !
failed to add the host (veth8af48a7) <=> sandbox (veth907cd9c) pair interfaces: operation not supported.
Maybe you're running with a kernel without CONFIG_VETH enabled or something. Your user's privileges do not matter, it is the docker daemon running as root that is failing to create the network interface.
As the issue is about privileges, I was wondering if it's about seatd, which is the one granting accesses.
seatd only grants input/output device access to your display server. It is not used by any other process, and does not interact with network adapters.
At any rate, as a thing about privileges, I doubt dbus has anything to do with it.
polkit, which uses dbus, is used for a lot of fine-grained privilege escalation, but a docker daemon running as root shouldn't need this.
Closing as unrelated to seatd.
ohh, this was a question more than an issue, since I don't have another way to get in contact. Sorry about that.
Now docker was working just fine with elogind, I'm trying to understand if it broke because of no longer using elogind in case it's the only way (I really doubt it), if it's because I need to do something special if not using seatd, or what else... So not really a kernel issue.
Thanks !