Hi, I'm running a service that only writes output to log file, not
configurable. Then I'm trying to link the log file to /dev/stdout but I
guess that is not enough to be received by journald because is not working.
As I've read here: https://github.com/coreos/rkt/issues/2640 really
/var/lib/machines/os --machine=foo -b -x
On Fri, Aug 19, 2016 at 1:02 PM, Lennart Poettering <lenn...@poettering.net>
> On Tue, 16.08.16 15:43, Juanjo Presa (juan...@gmail.com) wrote:
> > Hi, I'm trying to compose a container with several layers a
Hi, I'm trying to compose a container with several layers and join together
with overlay option but seems that is not supported.
I want to get something like:
systemd-nspawn --overlay=/foo/ubuntu-base:/foo/app-runtime:/foo/app:/ -D
Maybe I'm misunderstanding the overlay option.
I am comfortable with machinectl nowadays but maybe I miss some kind of
versioning of images generated. Do you have any advice or recommendation
On Thu, Oct 20, 2016 at 2:41 AM, Nathan Williams
> Fwiw, if you're using Chef, the impending release of v3
What about rkt with systemd?
On Thu, Oct 20, 2016 at 2:02 PM, Lennart Poettering <lenn...@poettering.net>
> On Thu, 20.10.16 12:35, Juanjo Presa (juan...@gmail.com) wrote:
I am researching about the different systems of transactional (atomic)
upgrades and rollbacks in linux. Namely, ubuntu core, rpm-ostree, coreos.
Which of them is more in line with the systemd philosophy? I personally
like the coreos chrome-based system based on GPT partitions, but I doubt
I am trying to run concourse CI (CI that run build process into
docker/runc/whatever containers) on systemd-nspawn. I will try to explain
what i do:
1.- First I make a .raw file that install/setup app (with mkosi).
2.- Run concourse container with "systemd-nspawn -bi concourse.raw
I wonder which ways are to run last systemd versions? nowadays Im running
Centos 7 with systemd facebook backports (
https://github.com/facebookincubator/rpm-backports). But maybe you guys
have another way, NixOs? Archlinux?