Re: [systemd-devel] container /proc/filesystems owned by nobody:can't upgrade

On 10/03/2017 05:19 PM, Mike Gilbert wrote: > On Tue, Oct 3, 2017 at 4:01 AM, arnaud gaboury > <arnaud.gabo...@gmail.com> wrote: >> My host is Archlinux, nspawn container is Fedora 26. Kernel is 4.13.3 >> I can't fully upgrade my container as some files are owned by &g

Re: [systemd-devel] container /proc/filesystems owned by nobody:can't upgrade

On 10/03/2017 04:35 PM, Anthony Joseph Messina wrote: > On Tuesday, October 3, 2017 3:01:25 AM CDT arnaud gaboury wrote: >> My host is Archlinux, nspawn container is Fedora 26. Kernel is 4.13.3 >> I can't fully upgrade my container as some files are owned by >> nobody:no

[systemd-devel] container /proc/filesystems owned by nobody:can't upgrade

My host is Archlinux, nspawn container is Fedora 26. Kernel is 4.13.3 I can't fully upgrade my container as some files are owned by nobody:nobody and can't change to root. An example is filesystems. When upgrading, it returns error: < error: unpacking of archive failed on file /proc: cpio: chown

[systemd-devel] access /proc of nspwan container

For some reasons (custom kernel with user namespace activated) my container filesystem owners and permissions has lots of errors. In short, some files/folders belong to nobody/nobody when in fact they should be owned by root:root. I can manage to partially fix things from the host where I can

Re: [systemd-devel] no user dbus session in container

On Wed, Jul 19, 2017 at 2:18 PM Simon McVittie <s...@collabora.com> wrote: > On Wed, 19 Jul 2017 at 09:31:36 +0000, arnaud gaboury wrote: > > Do I really need a per user dbsu session in my container? > > I don't know. Do you? You haven't said anything about how you

[systemd-devel] permissions issues in systemd machine

Here is my environment: Linux kernel 4.11.3 with usernamespace set to YES % systemctl --version systemd 233 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN default-hierarchy=hybrid % machinectl list

Re: [systemd-devel] no user dbus session in container

On Tue, Jul 18, 2017 at 3:09 PM Simon McVittie <s...@collabora.com> wrote: > On Fri, 14 Jul 2017 at 12:36:12 +0000, arnaud gaboury wrote: > > After upgrade from Fedora 25 to 26, there is no more user dbus session > for user > > in container. > ... > > On cont

[systemd-devel] no user dbus session in container

% systemctl --version systemd 233 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN default-hierarchy=hybrid % machinectl list MACHINE CLASS SERVICEOS VERSION ADDRESSES poppy container

Re: [systemd-devel] Systemd weird behavior after upgrade -

On Thu, Jul 13, 2017 at 11:58 PM Reindl Harald <h.rei...@thelounge.net> wrote: > > > Am 13.07.2017 um 23:40 schrieb arnaud gaboury: > > (no HTML crapps) > > still HTML and no meaningful quoting to distinct your "i respond to > myself" answer with you

[systemd-devel] Systemd weird behavior after upgrade -

(no HTML crapps) OS= Fedora 26 Linux container managed by machinectl % systemctl --version systemd 233 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN default-hierarchy=hybrid % machinectl list

Re: [systemd-devel] Systemd weird behavior after upgrade

On Thu, Jul 13, 2017 at 11:02 PM arnaud gaboury <arnaud.gabo...@gmail.com> wrote: > On Thu, Jul 13, 2017 at 2:27 PM arnaud gaboury <arnaud.gabo...@gmail.com> > wrote: > >> >> OS= Fedora 26 >> Linux container managed by machinectl >> >> % systemc

Re: [systemd-devel] Systemd weird behavior after upgrade

On Thu, Jul 13, 2017 at 2:27 PM arnaud gaboury <arnaud.gabo...@gmail.com> wrote: > > OS= Fedora 26 > Linux container managed by machinectl > > % systemctl --version > systemd 233 > +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP > +GCRYPT

[systemd-devel] Systemd weird behavior after upgrade

OS= Fedora 26 Linux container managed by machinectl % systemctl --version systemd 233 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN default-hierarchy=hybrid % machinectl list MACHINE CLASS SERVICE

Re: [systemd-devel] nsapwned container terminal background color

On Mon, Mar 20, 2017 at 5:12 AM Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote: > On Sun, Mar 19, 2017 at 09:30:05PM +, Zbigniew Jędrzejewski-Szmek > wrote: > > On Sun, Mar 19, 2017 at 04:37:53PM +0000, arnaud gaboury wrote: > > > I am trying with no suc

[systemd-devel] nsapwned container terminal background color

I am trying with no success to have one background terminal color for the host and another one for the container. Some settings: - on host: window manager : i3 terminal : urxvt-256 -on container: no X, it is a server. Until now, I have tried to write a wrapper script to urxvt on host. This

Re: [systemd-devel] news on Issue # 4078 ?

On Thu, Dec 15, 2016 at 7:27 PM Tomasz Torcz <to...@pipebreaker.pl> wrote: > On Thu, Dec 15, 2016 at 04:37:19PM +0000, arnaud gaboury wrote: > > I am still with a broken UID/GID container for some specific directories. > > This is described in issue #4078 [0]. > > >

[systemd-devel] UID/GID in nspawn container

Arch host running a nsapwn Fedora 25 container. On host, % systemctl --version systemd 232 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN % uname -r 4.8.13-1-hortensia <<--- custom one

[systemd-devel] news on Issue # 4078 ?

I am still with a broken UID/GID container for some specific directories. This is described in issue #4078 [0]. It start to be annoying as I can't upgrade some packages on the Fedora container. At least, I think failed upgrades are related to this issue. Let's take one example: # dnf upgrade

[systemd-devel] UID/GID broken on container

I am refering here to issue #4078[0] and see if I missed any progress. I am still with a broken UID on my container on some directories. Example: >From inside the container: --- $ ls -la /proc -rw-r--r-- 1 nobody nobody 0 Dec 12

Re: [systemd-devel] systemd-networkd: broken network in container

On Tue, Nov 22, 2016 at 4:54 PM arnaud gaboury <arnaud.gabo...@gmail.com> wrote: > Since a few days, after some upgrades, I don't have anymore network in my > container. Network is OK on my host > > --- > Host: Archlinux - > % systemctl --vers

[systemd-devel] systemd-networkd: broken network in container

Since a few days, after some upgrades, I don't have anymore network in my container. Network is OK on my host --- Host: Archlinux - % systemctl --version systemd 231 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4

Re: [systemd-devel] Broken network in container

On Fri, Nov 18, 2016 at 6:52 PM arnaud gaboury <arnaud.gabo...@gmail.com> wrote: > On Fri, Nov 18, 2016 at 4:03 PM arnaud gaboury <arnaud.gabo...@gmail.com> > wrote: > > On Fri, Nov 18, 2016 at 3:51 PM arnaud gaboury <arnaud.gabo...@gmail.com> > wrote: > >

Re: [systemd-devel] Broken network in container

On Fri, Nov 18, 2016 at 4:03 PM arnaud gaboury <arnaud.gabo...@gmail.com> wrote: > On Fri, Nov 18, 2016 at 3:51 PM arnaud gaboury <arnaud.gabo...@gmail.com> > wrote: > > A recent change (upgrade ?) in my setup broke the network in my container. >

Re: [systemd-devel] Broken network in container

On Fri, Nov 18, 2016 at 3:51 PM arnaud gaboury <arnaud.gabo...@gmail.com> wrote: > A recent change (upgrade ?) in my setup broke the network in my container. > Network is OK on the host, but not on the container. > > My setup: > > Host: Archlinux - > % systemctl --v

[systemd-devel] Broken network in container

A recent change (upgrade ?) in my setup broke the network in my container. Network is OK on the host, but not on the container. My setup: Host: Archlinux - % systemctl --version systemd 231 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4

Re: [systemd-devel] moving a directory let me with a 65534:65534 owner/group directory

On Thu, Sep 1, 2016 at 4:24 PM arnaud gaboury <arnaud.gabo...@gmail.com> wrote: > On Thu, Sep 1, 2016 at 2:02 PM Lennart Poettering <lenn...@poettering.net> > wrote: > >> On Thu, 01.09.16 10:47, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: >> >> >

Re: [systemd-devel] moving a directory let me with a 65534:65534 owner/group directory

On Thu, Sep 1, 2016 at 2:02 PM Lennart Poettering <lenn...@poettering.net> wrote: > On Thu, 01.09.16 10:47, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > > > I have been moving directories and files between my host and my container > > many times since more than one y

Re: [systemd-devel] moving a directory let me with a 65534:65534 owner/group directory

On Thu, Sep 1, 2016 at 12:47 PM arnaud gaboury <arnaud.gabo...@gmail.com> wrote: > I have been moving directories and files between my host and my container > many times since more than one year with no issues. Host is Archlinux and > container Fedora 24 (upgrade to 24 is quite

[systemd-devel] moving a directory let me with a 65534:65534 owner/group directory

I have been moving directories and files between my host and my container many times since more than one year with no issues. Host is Archlinux and container Fedora 24 (upgrade to 24 is quite recent: no more than 2 months). I moved a directory today from host to container and this let me, for the

Re: [systemd-devel] Timer: time format

On Tue, Aug 23, 2016 at 3:39 PM, Michael Chapman <m...@very.puzzling.org> wrote: > On Tue, 23 Aug 2016, arnaud gaboury wrote: >> >> I am really sorry for this post as this may sound like a trivial one, >> but honestly the timer topic is difficult to understand for me (

Re: [systemd-devel] Timer: time format

On Tue, Aug 23, 2016 at 3:52 PM, arnaud gaboury <arnaud.gabo...@gmail.com> wrote: > On Tue, Aug 23, 2016 at 3:39 PM, Michael Chapman <m...@very.puzzling.org> > wrote: >> On Tue, 23 Aug 2016, arnaud gaboury wrote: >>> >>> I am really sorry for this

[systemd-devel] Timer: time format

I am really sorry for this post as this may sound like a trivial one, but honestly the timer topic is difficult to understand for me (at least the time format). I am looking to run a service twice a day, never mind the time. I understand I must use OnCalendar, but I have no idea for the rest. I

Re: [systemd-devel] nspawn container: network broken

On Fri, Aug 12, 2016 at 2:20 PM, arnaud gaboury <arnaud.gabo...@gmail.com> wrote: > Host distro: arch linux running systemd 230 > container distro Fedora 24 running systemd 229 > > I broke systemd-networkd on the host after an upgrade to 231-1. The > issue was the one descri

[systemd-devel] nspawn container: network broken

Host distro: arch linux running systemd 230 container distro Fedora 24 running systemd 229 I broke systemd-networkd on the host after an upgrade to 231-1. The issue was the one described here[0]. In order to get back my network, I downgraded to 230 and now network is working on host, BUT still

[systemd-devel] systemd-networkd - Could not append VLANs / operation not permitted

- Systemd version 213-1 - OS: Arch linux - a systemd nspawn container is running - host network is managed by systemd-networkd After an upgrade, systemd-networkd is broken, exactly the way descibed in this issue #3876[0] Everything was working pefectly before. Config files:

Re: [systemd-devel] sshd.socket: connection closed by remote host

On Sat, Mar 19, 2016 at 3:00 PM, arnaud gaboury <arnaud.gabo...@gmail.com> wrote: > OS: fedora 23 server > systemd: 222 > > I gave a try at sshd.socket instead of the usual sshd.service. The latter > was working well on my server but I can't ssh with sshd.socket. > >

Re: [systemd-devel] sshd.socket: connection closed by remote host

On Sat, Mar 19, 2016 at 3:00 PM, arnaud gaboury <arnaud.gabo...@gmail.com> wrote: > OS: fedora 23 server > systemd: 222 > > I gave a try at sshd.socket instead of the usual sshd.service. The latter > was working well on my server but I can't ssh with sshd.socket. > >

[systemd-devel] sshd.socket: connection closed by remote host

OS: fedora 23 server systemd: 222 I gave a try at sshd.socket instead of the usual sshd.service. The latter was working well on my server but I can't ssh with sshd.socket. % systemctl cat sshd.socket -- # /usr/lib/systemd/system/sshd.socket [Unit]

Re: [systemd-devel] Environment and additional command line options

On Mon, Feb 1, 2016 at 10:48 AM, Mantas Mikulėnas <graw...@gmail.com> wrote: > On Mon, Feb 1, 2016 at 11:37 AM, arnaud gaboury <arnaud.gabo...@gmail.com> > wrote: >> >> $ systemctl --version >> systemd 22 > > > v22 was released five years ago, are you

[systemd-devel] Environment and additional command line options

$ systemctl --version systemd 22 One way to pass additional options is to add one of these lines in the [Service] part of the unit file: Environment=ONE='one' EnvironmentFile=/path/to --- If I am right, there is another possible mechanism since recent versions by

Re: [systemd-devel] Fwd: messing with .mount/.automount units

On Sat, Jan 30, 2016, 5:28 PM Andrei Borzenkov <arvidj...@gmail.com> wrote: > 30.01.2016 13:44, arnaud gaboury пишет: > >>> My first attempt was to add this line in my /etc/fstab: > >>> --- > >>&

Re: [systemd-devel] Fwd: messing with .mount/.automount units

On Sat, Jan 30, 2016 at 8:11 AM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > 29.01.2016 23:07, arnaud gaboury пишет: >> BUMP. >> >> I run once a week a simple backup with rsync. For that purpose, I >> wrote a service file (rsync) and a timer unit. They both wo

[systemd-devel] Fwd: messing with .mount/.automount units

BUMP. I run once a week a simple backup with rsync. For that purpose, I wrote a service file (rsync) and a timer unit. They both work with no issues. /etc/systemd/system/backup-external.service [Unit] Description=Backup system to external

[systemd-devel] messing with .mount/.automount units

I run once a week a simple backup with rsync. For that purpose, I wrote a service file (rsync) and a timer unit. They both work with no issues. /etc/systemd/system/backup-external.service [Unit] Description=Backup system to external drive

Re: [systemd-devel] On calendar timer

On Tue, Jan 12, 2016 at 6:46 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Wed, 06.01.16 17:17, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> I am not sure about how to express date/time in a timer unit. >> >> I want the timer to be start every

[systemd-devel] On calendar timer

I am not sure about how to express date/time in a timer unit. I want the timer to be start every year(*), on month 1,3,5,7,9,11, first day of month at 02:00:00 AM. Here is what I wrote: [Timer] OnCalendar=*-1,3,5,7,9,11-01 02:00:00 Is this correct ? Now if I want instead not the first day of

Re: [systemd-devel] empty a directory in service file as ExecStartPre

rdle. Will post elsewhere as it is OT in this list. Thank you for your help. > > Alternatively 'sh -c "rm .../*" to handle wildcards. > > > On Sat, Jan 2, 2016, 13:39 arnaud gaboury <arnaud.gabo...@gmail.com> wrote: >> >> I can't manage to empt

Re: [systemd-devel] empty a directory in service file as ExecStartPre

On Sat, Jan 2, 2016 at 1:57 PM, Reindl Harald <h.rei...@thelounge.net> wrote: > > > Am 02.01.2016 um 13:43 schrieb arnaud gaboury: >> >> ExecStartPre=/usr/bin/rm -f ${REPORTDIR}/ > > > ExecStartPre=/usr/local/scripts/emptydir.sh $REPORTDIR Thank you, but

[systemd-devel] empty a directory in service file as ExecStartPre

I can't manage to empty a directory as a Exec in a service file. Here is part: --- [Service] User=postgres Environment=REPORTDIR=/storage/psqlReport ExecStartPre=/usr/bin/rm -f ${REPORTDIR}/* ExecStart=MyCommand

[systemd-devel] systemd nspawn container - download speed slow

Here is my setup: Arch host Fedora 23 nspawn container Network: From host: --- % ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo

Re: [systemd-devel] modules in container

On Sun, Nov 8, 2015 at 2:57 PM Richard Weinberger < richard.weinber...@gmail.com> wrote: > On Sun, Nov 8, 2015 at 1:17 PM, arnaud gaboury <arnaud.gabo...@gmail.com> > wrote: > > I am trying to understand how kernel modules are "passed" to nspawn > contain

[systemd-devel] modules in container

I am trying to understand how kernel modules are "passed" to nspawn container. My setup: Archlinux host, Fedora 23 container (function = server). Example of what I would like to solve: On container: -- $ systemctl

[systemd-devel] upgrade a Fedora container 22 > 23

For those of us who are wondering if this can be tricky, I just want to testify you just have to follow Fedora instruction[1] and restart the machine. No issues at all and Fedora will be upgraded to 23. You need to wait a little bit (~ 5-10 mn) after you run # dnf system-upgrade reboot for the

Re: [systemd-devel] Machinectl shell/login do not attach to console

Honestly, I don't think your issue has to do with the container systemd version. On my host, archlinux: systemd 227-1 On my container, Fedora 22: sysetemd 219 - # machinectl login poppy [sudo] password for gabx: Connected to machine poppy. Press ^] three

Re: [systemd-devel] Machinectl shell/login do not attach to console

On Mon, Oct 5, 2015 at 2:30 PM, Chris Bell wrote: > Hi all, > > I have an Arch machine with systemd 226, which arch version exactly? I had the same issue with 226. It is gone with 226-3. setup: Arch host running Fedora container. running an Arch container, also > with systemd

[systemd-devel] machinectl shell

First, thank you for this new feature. I do think this is a much more clean way to log as root. I just can't get the correct shell, which is /bin/zsh: /etc/passwd --- root:x:0:0:root:/root:/usr/bin/zsh - $ machinectl shell brings me to sh.

Re: [systemd-devel] machinectl shell

On Sun, Oct 4, 2015 at 11:34 AM, Tobias Hunger <tobias.hun...@gmail.com> wrote: > Hi Arnaud, > > Am 04.10.2015 11:27 schrieb "arnaud gaboury" <arnaud.gabo...@gmail.com>: >> >> First, thank you for this new feature. I do think this is a much more >>

Re: [systemd-devel] machinectl shell

On Sun, Oct 4, 2015 at 11:49 AM, Tomasz Torcz <to...@pipebreaker.pl> wrote: > On Sun, Oct 04, 2015 at 11:27:20AM +0200, arnaud gaboury wrote: >> First, thank you for this new feature. I do think this is a much more >> clean way to log as root. >> >> I just c

[systemd-devel] /etc/dbus-1/session-local.conf

As I am trying to improve my knowledges in how dbus work, I discovered this file in /etc/dbus-1/session-local.conf unix:path=/run/user/1000/dbus/user_bus_socket -- I Can't remember editing it, but I must have done it. I understand it overrides

Re: [systemd-devel] Multi seats setup How-to

On Sun, Sep 6, 2015 at 3:36 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Sun, 06.09.15 13:14, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> On Sun, Sep 6, 2015 at 1:08 PM, Lennart Poettering >> <lenn...@poettering.net> wrote: >> >

Re: [systemd-devel] Multi seats setup How-to

On Sun, Sep 6, 2015 at 4:19 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Sun, 06.09.15 16:02, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> > That's awfully generic... >> > >> > I'd really just be interested in vendor/product ids if t

Re: [systemd-devel] Multi seats setup How-to

On Sun, Sep 6, 2015 at 1:08 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Sun, 06.09.15 13:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> On Sun, Sep 6, 2015 at 12:53 PM, Lennart Poettering >> <lenn...@poettering.net> wrote: >> >

Re: [systemd-devel] Multi seats setup How-to

On Sun, Sep 6, 2015 at 12:53 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Thu, 03.09.15 13:26, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> I plan to use the systemd mutli-seat features, but I am not sure at >> all how I must proceed and in waht orde

Re: [systemd-devel] Multi seats setup How-to

On Sun, Sep 6, 2015 at 6:53 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Sun, 06.09.15 18:24, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> On Sun, Sep 6, 2015 at 5:22 PM, Lennart Poettering >> <lenn...@poettering.net> wrote: >> >

Re: [systemd-devel] Multi seats setup How-to

On Sun, Sep 6, 2015 at 5:22 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Sun, 06.09.15 16:31, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > > I fear this newer Plugable device is not as carefully designed as the > older ones, and uses non-recognizable v

Re: [systemd-devel] Multi seats setup How-to

On Thu, Sep 3, 2015 at 5:06 PM, arnaud gaboury <arnaud.gabo...@gmail.com> wrote: > > On Thu, Sep 3, 2015, 3:46 PM Floris <jkflo...@dds.nl> wrote: > >> >> I was missing one piece of the puzzle. My USB dock statio

Re: [systemd-devel] Multi seats setup How-to

On Thu, Sep 3, 2015, 3:46 PM Floris wrote: > > I was missing one piece of the puzzle. My USB dock station is > Plugable® UD-3900 USB 3.0 > > > 1- > I had to install the kernel driver for it, following instructions per >

Re: [systemd-devel] Multi seats

gt; > 2015-08-28 8:42 GMT-03:00 arnaud gaboury <arnaud.gabo...@gmail.com>: > >> On Fri, Aug 28, 2015 at 1:37 PM, Laércio de Sousa >> <laercioso...@sme-mogidascruzes.sp.gov.br> wrote: >> > Hi Arnaud! >> > >> > I've been researching systemd

[systemd-devel] Multi seats setup How-to

I plan to use the systemd mutli-seat features, but I am not sure at all how I must proceed and in waht order. I understand the main principle for mouse and keyboard: detect the device then $ loginctl attach seatNumber DevicePath As for the graphic card, I am lost. OS: Fedora 22 gdm 1 nvidia card

Re: [systemd-devel] Multi seats setup How-to

On Thu, Sep 3, 2015 at 1:26 PM, arnaud gaboury <arnaud.gabo...@gmail.com> wrote: > I plan to use the systemd mutli-seat features, but I am not sure at > all how I must proceed and in waht order. I understand the main > principle for mouse and keyboard: detect the device then >

Re: [systemd-devel] Multi seats setup How-to

On Thu, Sep 3, 2015 at 2:12 PM, Floris <jkflo...@dds.nl> wrote: > Op Thu, 03 Sep 2015 13:51:06 +0200 schreef arnaud gaboury > <arnaud.gabo...@gmail.com>: > >> On Thu, Sep 3, 2015 at 1:26 PM, arnaud gaboury <arnaud.gabo...@gmail.com> >> wrote: >>> &

[systemd-devel] Kdbus - dbus daemon

Distro : Arch Systemd : 224 Kdbus AUR package installed (kdbus module is not in default Arch Kernel) nspawn container : Fedora 22, systemd 219 I want to give a try to kdbus. If I read correctly the kdbus[0] website: . Am I right to understand I will no more need dbus.service and I can disable it

Re: [systemd-devel] Multi seats

GNOME) In fact I was wrong in my presentation. Login window is now managed by GDM in Fedora 22, not Lightdm. I guess I do not need to install and log with Lightdm, am I right? Att. 2015-08-28 7:58 GMT-03:00 arnaud gaboury arnaud.gabo...@gmail.com: One year ago, I tried to setup multi seats

[systemd-devel] Multi seats

One year ago, I tried to setup multi seats, see this thread[0]. By that time, I gave up as my configuration was not made for such a fetaure. Now I am back with all the needed tools to do it easily (I think so): - Fedora 22 - lightdm GDM - an USB 3 plugable dockin station As good how-to on this

Re: [systemd-devel] SElinux in container

On Mon, Aug 24, 2015 at 1:30 PM, Daniel J Walsh dwa...@redhat.com wrote: On 08/23/2015 08:10 AM, arnaud gaboury wrote: Here is my setup: Host: Archlinux systemd 224-1 Container: Fedora 22 systemd 219 The container is a server and has vocation to be one day deployed on a dediacted server

[systemd-devel] SElinux in container

Here is my setup: Host: Archlinux systemd 224-1 Container: Fedora 22 systemd 219 The container is a server and has vocation to be one day deployed on a dediacted server for production. In this way, I would like to set SElinux (default in Fedora). Unfortunately, doing it in Arch host is not a

Re: [systemd-devel] error when starting the service : Bad message

On Tue, May 19, 2015 at 9:05 AM, arnaud gaboury arnaud.gabo...@gmail.com wrote: I maybe did a typo, but looking carefully it doesn't seems so. Starting this unit file gives me: - ● gunicorn.service - gunicorn daemon Loaded

[systemd-devel] error when starting the service : Bad message

I maybe did a typo, but looking carefully it doesn't seems so. Starting this unit file gives me: - ● gunicorn.service - gunicorn daemon Loaded: error (Reason: Bad message) Active: inactive (dead) May 19 08:45:53 poppy

Re: [systemd-devel] dbus inside nspawn container

On Fri, May 15, 2015 at 2:21 PM, Dimitri John Ledkov dimitri.j.led...@intel.com wrote: On 15 May 2015 at 13:07, arnaud gaboury arnaud.gabo...@gmail.com wrote: Maybe a stupid question, but shall every container user start a per user dbus session ? Host has a dbus and user session activated

[systemd-devel] dbus inside nspawn container

Maybe a stupid question, but shall every container user start a per user dbus session ? Host has a dbus and user session activated, shall it be same in container? Thank you for hints -- google.com/+arnaudgabourygabx ___ systemd-devel mailing list

Re: [systemd-devel] dbus inside nspawn container

On Fri, May 15, 2015, 4:22 PM Simon McVittie simon.mcvit...@collabora.co.uk wrote: On 15/05/15 14:17, Lennart Poettering wrote: On Fri, 15.05.15 14:07, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: Maybe a stupid question, but shall every container user start a per user dbus session

[systemd-devel] networkd must start before nspawn@container

My host/conatiner networking are both managed by systemd-netwrokd. I have a bridge Br0 on host and vb-MyContainer for the conatiner. Both have a fix local IP. I boot container at host boot this way: -- $ cat /etc/systemd/system/systemd-nspawn@.service

[systemd-devel] mount crypto_LUKS device in conatiner

My container will need access to a Luks encrypted device (/dev/sdd4) for its DB. Here is the setup on the host : - # cryptsetup --key-file /etc/keys/poppy.luks luksOpen /dev/bcache0 sdd4_crypt $ lsblk -o NAME,KNAME,MAJ:MIN,FSTYPE,LABEL

[systemd-devel] network interface down in container

I already used for a while a container (Arch on Arch). I had two distinct IP and a working setup thanks to good help from Tom Gundersen I am trying to replicate my network settings on a new setup (Fedora on Arch). For now, I am just trying with DHCP. Here the setup on host:

Re: [systemd-devel] network interface down in container

On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering lenn...@poettering.net wrote: On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: I used to boot the container this way : # systemd-nspawn --network-bridge=br0 -bD /path_to/my_container Is this correct? Looks fine

Re: [systemd-devel] network interface down in container

On Thu, Apr 30, 2015 at 12:18 PM, arnaud gaboury arnaud.gabo...@gmail.com wrote: On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering lenn...@poettering.net wrote: On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: I used to boot the container this way : # systemd

Re: [systemd-devel] network interface down in container

On Thu, Apr 30, 2015 at 12:48 PM, arnaud gaboury arnaud.gabo...@gmail.com wrote: On Thu, Apr 30, 2015 at 12:18 PM, arnaud gaboury arnaud.gabo...@gmail.com wrote: On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering lenn...@poettering.net wrote: On Thu, 30.04.15 10:01, arnaud gaboury

Re: [systemd-devel] network interface down in container

On Thu, Apr 30, 2015, 2:22 PM Lennart Poettering lenn...@poettering.net wrote: On Thu, 30.04.15 12:48, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: E2978F 2: host0 Link File: n/a Network File: n/a Type: ether State: off (unmanaged) HW Address: 0e:7f:c3:fb:25

[systemd-devel] Basic network with Fedora conatiner

After installation of Fedora 22 container, the container (poppy) boots but no network. # journalctl -b -M poppy Apr 29 14:02:20 poppy firewalld[28]: 2015-04-29 14:02:20 ERROR: ebtables not usable, disabling ethernet bridge firewall. Apr 29 14:02:20 poppy NetworkManager[56]: warn

Re: [systemd-devel] Basic network with Fedora conatiner

On Wed, Apr 29, 2015 at 4:48 PM, Dan Williams d...@redhat.com wrote: On Wed, 2015-04-29 at 15:36 +0200, arnaud gaboury wrote: After installation of Fedora 22 container, the container (poppy) boots but no network. # journalctl -b -M poppy Apr 29 14:02:20 poppy

Re: [systemd-devel] Fedora on systemd-nspawn container - ML best practice

On Tue, Apr 28, 2015, 11:38 AM Lennart Poettering mzerq...@0pointer.de wrote: On Tue, 28.04.15 09:31, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: I started running Fedora server on a systemd-nspawn container. I am wondering what is the best practice when an issue occurs: - send

[systemd-devel] Fedora on systemd-nspawn container - ML best practice

I started running Fedora server on a systemd-nspawn container. I am wondering what is the best practice when an issue occurs: - send to Fedora user ML - send to systemd-devel ML - send both with CC I am afraid that when sending to only one list I will be told to ask the other one, thus wasting

[systemd-devel] systemd-nspawn -- bind multiple directories

To install a Fedora container from the raw image in my host Archlinux, I can do this: # systemd-nspawn -M Fedora-Cloud-Base-22_Beta-20150415.x86_64.raw -- bind=/var/lib/machines/enl:/mnt Now for the use of two btrfs subvol, I would like to bind /var/lib/machines/enl/{etc,var} Does the systemd

Re: [systemd-devel] systemd-nspawn -- bind multiple directories

On Mon, Apr 27, 2015 at 3:44 PM, Lennart Poettering lenn...@poettering.net wrote: On Mon, 27.04.15 10:19, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: To install a Fedora container from the raw image in my host Archlinux, I can do this: # systemd-nspawn -M Fedora-Cloud-Base-22_Beta

Re: [systemd-devel] systemd-nspawn -- bind multiple directories

On Mon, Apr 27, 2015 at 3:44 PM, Lennart Poettering lenn...@poettering.net wrote: On Mon, 27.04.15 10:19, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: To install a Fedora container from the raw image in my host Archlinux, I can do this: # systemd-nspawn -M Fedora-Cloud-Base-22_Beta

Re: [systemd-devel] install Fedora systemd-nspawn container on btrfs

On Fri, Apr 24, 2015 at 8:16 AM, arnaud gaboury arnaud.gabo...@gmail.com wrote: On Fri, Apr 24, 2015 at 8:14 AM, arnaud gaboury arnaud.gabo...@gmail.com wrote: On Thu, Apr 23, 2015 at 7:37 PM, arnaud gaboury arnaud.gabo...@gmail.com wrote: On Thu, Apr 23, 2015 at 7:36 PM, Lennart Poettering

Re: [systemd-devel] install Fedora systemd-nspawn container on btrfs

On Fri, Apr 24, 2015 at 8:14 AM, arnaud gaboury arnaud.gabo...@gmail.com wrote: On Thu, Apr 23, 2015 at 7:37 PM, arnaud gaboury arnaud.gabo...@gmail.com wrote: On Thu, Apr 23, 2015 at 7:36 PM, Lennart Poettering lenn...@poettering.net wrote: On Thu, 23.04.15 19:29, arnaud gaboury (arnaud.gabo

Re: [systemd-devel] install Fedora systemd-nspawn container on btrfs

On Thu, Apr 23, 2015 at 7:37 PM, arnaud gaboury arnaud.gabo...@gmail.com wrote: On Thu, Apr 23, 2015 at 7:36 PM, Lennart Poettering lenn...@poettering.net wrote: On Thu, 23.04.15 19:29, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: When in /var/lib/machines/poppy: root@hortensia

Re: [systemd-devel] install Fedora systemd-nspawn container on btrfs

On Thu, Apr 23, 2015 at 7:36 PM, Lennart Poettering lenn...@poettering.net wrote: On Thu, 23.04.15 19:29, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: When in /var/lib/machines/poppy: root@hortensia ➤➤ machines/poppy # btrfs subvolume list . ID 266 gen 98 top level 5 path rootvol ID 268

Re: [systemd-devel] install Fedora systemd-nspawn container on btrfs

On Thu, Apr 23, 2015 at 7:21 PM, arnaud gaboury arnaud.gabo...@gmail.com wrote: On Thu, Apr 23, 2015 at 7:12 PM, Lennart Poettering lenn...@poettering.net wrote: On Thu, 23.04.15 19:00, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: On Thu, Apr 23, 2015 at 4:47 PM, Lennart Poettering lenn

  1   2   >