On 10/03/2017 05:19 PM, Mike Gilbert wrote:
> On Tue, Oct 3, 2017 at 4:01 AM, 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:nobody and can&#x
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:
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 >
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 chown
On Wed, Jul 19, 2017 at 2:18 PM Simon McVittie 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 start the
> containe
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
MACH
On Tue, Jul 18, 2017 at 3:09 PM Simon McVittie 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 container, user can't connec
% 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 sys
On Thu, Jul 13, 2017 at 11:58 PM Reindl Harald
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 your initial post - no idea what you ex
(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
MACHINE
On Thu, Jul 13, 2017 at 11:02 PM arnaud gaboury
wrote:
> On Thu, Jul 13, 2017 at 2:27 PM arnaud gaboury
> wrote:
>
>>
>> OS= Fedora 26
>> Linux container managed by machinectl
>>
>> % systemctl --version
>> systemd 233
>> +PAM -A
On Thu, Jul 13, 2017 at 2:27 PM arnaud gaboury
wrote:
>
> 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 -SECCOM
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
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
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
scrip
On Thu, Dec 15, 2016 at 7:27 PM Tomasz Torcz 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].
> >
> > It start to be annoy
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
---
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 iput
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 11:4
On Tue, Nov 22, 2016 at 4:54 PM arnaud gaboury
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 --version
> systemd 231
&
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
On Fri, Nov 18, 2016 at 6:52 PM arnaud gaboury
wrote:
> On Fri, Nov 18, 2016 at 4:03 PM arnaud gaboury
> wrote:
>
> On Fri, Nov 18, 2016 at 3:51 PM arnaud gaboury
> wrote:
>
> A recent change (upgrade ?) in my setup broke the network in my container.
> Network is OK on
On Fri, Nov 18, 2016 at 4:03 PM arnaud gaboury
wrote:
> On Fri, Nov 18, 2016 at 3:51 PM arnaud gaboury
> 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
On Fri, Nov 18, 2016 at 3:51 PM arnaud gaboury
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 --version
> systemd 231
>
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 +SE
On Thu, Sep 1, 2016 at 4:24 PM arnaud gaboury
wrote:
> On Thu, Sep 1, 2016 at 2:02 PM Lennart Poettering
> 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 m
On Thu, Sep 1, 2016 at 2:02 PM Lennart Poettering
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 year with no issues. Hos
On Thu, Sep 1, 2016 at 12:47 PM arnaud gaboury
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 recent: no more than 2 months).
&g
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
On Tue, Aug 23, 2016 at 3:39 PM, Michael Chapman 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 (at
>> least the time for
On Tue, Aug 23, 2016 at 3:52 PM, arnaud gaboury
wrote:
> On Tue, Aug 23, 2016 at 3:39 PM, Michael Chapman
> 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 h
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 w
On Fri, Aug 12, 2016 at 2:20 PM, arnaud gaboury
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 described here[0]. In order to get back
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
bro
- 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:
/etc/systemd/system/n
On Sat, Mar 19, 2016 at 3:00 PM, arnaud gaboury
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.
>
> %
On Sat, Mar 19, 2016 at 3:00 PM, arnaud gaboury
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.
>
> %
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]
Descr
On Mon, Feb 1, 2016 at 10:48 AM, Mantas Mikulėnas wrote:
> On Mon, Feb 1, 2016 at 11:37 AM, arnaud gaboury
> wrote:
>>
>> $ systemctl --version
>> systemd 22
>
>
> v22 was released five years ago, are you sure?
222, sorry for the typo
>
>>
>>
$ 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 ad
On Sat, Jan 30, 2016, 5:28 PM Andrei Borzenkov wrote:
> 30.01.2016 13:44, arnaud gaboury пишет:
> >>> My first attempt was to add this line in my /etc/fstab:
> >>> ---
> >>> UUID=868560c1-ab69-423f-b76d-b8
On Sat, Jan 30, 2016 at 8:11 AM, Andrei Borzenkov 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 work with no
>> issues.
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 driv
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
Requi
On Tue, Jan 12, 2016 at 6:46 PM, Lennart Poettering
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 year(*), on month 1,3,5,7,9,1
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 th
On Sat, Jan 2, 2016 at 1:57 PM, Reindl Harald 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 I would prefer to avoid any externa
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 wrote:
>>
>> I can't m
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
-
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
valid_lft forever pref
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
> wrote:
> > I am trying to understand how kernel modules are "passed" to nspawn
> container.
>
> A container must n
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 statu
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 sys
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 time
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 226. For whatever re
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
On Sun, Oct 4, 2015 at 11:49 AM, Tomasz Torcz 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 can't get the correct shel
On Sun, Oct 4, 2015 at 11:34 AM, Tobias Hunger wrote:
> Hi Arnaud,
>
> Am 04.10.2015 11:27 schrieb "arnaud gaboury" :
>>
>> First, thank you for this new feature. I do think this is a much more
>> clean way to log as root.
>>
>> I just can'
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.
On Sun, Sep 6, 2015 at 6:53 PM, Lennart Poettering
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
>> wrote:
>> > On Sun, 06.09.15 16:31, arnaud gaboury (arnaud.gabo...@gmail.c
On Sun, Sep 6, 2015 at 6:00 PM, Lennart Poettering
wrote:
> On Sun, 06.09.15 17:49, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
>
>> Hello.
>>
>> Is systemd-nspawn intended to eventually become usable for full system
>> containers/general use with enough security to run things like vps hostin
On Sun, Sep 6, 2015 at 5:22 PM, Lennart Poettering
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 vendor/product ids... Thus we
> ca
On Sun, Sep 6, 2015 at 4:19 PM, Lennart Poettering
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 the usb hub
>>
On Sun, Sep 6, 2015 at 3:36 PM, Lennart Poettering
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
>> wrote:
>> > On Sun, 06.09.15 13:01, arnaud gaboury (arnaud.gabo...@gmail.co
On Sun, Sep 6, 2015 at 1:08 PM, Lennart Poettering
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
>> wrote:
>> > On Thu, 03.09.15 13:26, arnaud gaboury (arnaud.gabo...@gmail.co
On Sun, Sep 6, 2015 at 12:53 PM, Lennart Poettering
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 order. I understand the main
>
On Sat, Sep 5, 2015 at 4:20 PM, Tobias Hunger wrote:
> Hello,
>
> I just upgraded to systemd 226 in the hope that machinectl shell will
> work better for me than machinectl login. Unfortunately it is not and
> machinectl login is also unusable:-/
>
> Both produce the "Connected to machine X. Press
On Fri, Sep 4, 2015 at 9:36 PM, Floris wrote:
>
>> I can't create a new seat1, no idea why.
>>
>> Here is my current configuration:
>>
>> -nvidia card + nvidia driver + nouveau blacklisted
>> - USB 3 dock station with displaylink driver + systemd service
>> - gdm
>> - systemd 219
>>
>>
>>
On Thu, Sep 3, 2015 at 5:06 PM, arnaud gaboury wrote:
>
> 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
>>
>> ---
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
> this displaylink for
On Thu, Sep 3, 2015 at 2:12 PM, Floris wrote:
> Op Thu, 03 Sep 2015 13:51:06 +0200 schreef arnaud gaboury
> :
>
>> On Thu, Sep 3, 2015 at 1:26 PM, arnaud gaboury
>> wrote:
>>>
>>> I plan to use the systemd mutli-seat features, but I am not sure at
>>
On Thu, Sep 3, 2015 at 1:26 PM, arnaud gaboury 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
> $ loginctl attach seatNumber Dev
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
1
IP.
>
> 2015-08-28 8:42 GMT-03:00 arnaud gaboury :
>
>> On Fri, Aug 28, 2015 at 1:37 PM, Laércio de Sousa
>> wrote:
>> > Hi Arnaud!
>> >
>> > I've been researching systemd-based multi-seat setups with non-KMS video
>> > drivers for a
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
able xorg.conf for your NVIDIA card, not forgetting to put
> MatchSeat entries in Device/Screen/ServerLayout sections.
>
> * Have LightDM 1.12 or newer installed (if you don't use GNOME)
In fact I was wrong in my presentation. Login window is now managed by
GDM in Fedora 22, not L
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 t
On Mon, Aug 24, 2015 at 1:30 PM, Daniel J Walsh 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
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 tri
On Tue, May 19, 2015 at 9:05 AM, arnaud gaboury
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
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 systemd[1]
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 p
On Fri, May 15, 2015 at 2:21 PM, Dimitri John Ledkov
wrote:
> On 15 May 2015 at 13:07, arnaud gaboury wrote:
>> 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 conta
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
syst
On Sat, May 2, 2015 at 11:27 AM, arnaud gaboury
wrote:
>
> 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 h
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
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
On Thu, Apr 30, 2015, 2:22 PM Lennart Poettering
wrote:
On Thu, 30.04.15 12:48, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
> > <97><8F> 2: host0
> >Link File: n/a
> > Network File: n/a
> > Type: ether
> >State: off (unma
On Thu, Apr 30, 2015 at 12:48 PM, arnaud gaboury
wrote:
> On Thu, Apr 30, 2015 at 12:18 PM, arnaud gaboury
> wrote:
>> On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering
>> wrote:
>>> On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
On Thu, Apr 30, 2015 at 12:18 PM, arnaud gaboury
wrote:
> On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering
> wrote:
>> On Thu, 30.04.15 10:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
>>
>>> I used to boot the container this way :
>>> # sys
On Thu, Apr 30, 2015 at 11:44 AM, Lennart Poettering
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
>>
>> I
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:
-
On Wed, Apr 29, 2015 at 4:48 PM, Dan Williams 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
> > ..
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]: Cou
On Tue, Apr 28, 2015, 11:38 AM Lennart Poettering
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 to Fe
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 ti
On Mon, Apr 27, 2015 at 3:44 PM, Lennart Poettering
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-Clou
On Mon, Apr 27, 2015 at 3:44 PM, Lennart Poettering
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-Clou
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 bi
On Fri, Apr 24, 2015 at 8:16 AM, arnaud gaboury
wrote:
> On Fri, Apr 24, 2015 at 8:14 AM, arnaud gaboury
> wrote:
>> On Thu, Apr 23, 2015 at 7:37 PM, arnaud gaboury
>> wrote:
>>> On Thu, Apr 23, 2015 at 7:36 PM, Lennart Poettering
>>> wrote:
>>
1 - 100 of 183 matches
Mail list logo
