Re: [systemd-devel] dockerd broken docker works without It own docker image but need

[Andy Pieters]

Dorian

All of us on this list here are wondering the same thing.

Where do you get your ideas from?!

 To clarify, systemd is not an engine for any other software such as apache
or MySQL
and the name ending in 'd' does not imply systemd.

E.g. mongod (Mongo db) not systemd, firewalld not systemd, dockerd, not
systemd etc

Systemd starts/stops/monitors daemons etc, but is not actually involved in
writing those daemons.
If you have apache that's failing to start, look in the apache logs, ask on
the apache mailing list etc.

Please Dorian, don't post to this list for troubles with mcelog or apache.
You're very welcome to ask us questions about systemd itself

Read up on systemd on Wikipedia

Here is the article in French: https://fr.wikipedia.org/wiki/Systemd

And a website talking about how to create services and timers :
https://www.linuxtricks.fr/wiki/systemd-creer-des-services-timers-unites

I hope this finally helps for you Dorian



On Fri, 27 Mar 2020 at 22:03, Andy Pieters  wrote:

>
> Dorian
>
>
> All of us on this list here are wondering the same thing.
>
> Where do you get your ideas from?!
>
>  To clarify, systemd is not an engine for any other software such as
> apache or MySQL
> and the name ending in 'd' does not imply systemd.
>
> E.g. mongod (Mongo db) not systemd, firewalld not systemd, dockerd, not
> systemd etc
>
> Systemd starts/stops/monitors daemons etc, but is not actually involved in
> writing those daemons.
> If you have apache that's failing to start, look in the apache logs, ask
> on the apache mailing list etc.
>
> Please Dorian, don't post to this list for troubles with mcelog or apache.
> You're very welcome to ask us questions about systemd itself
>
> Read up on systemd on Wikipedia
>
> Here is the article in French: https://fr.wikipedia.org/wiki/Systemd
>
> And a website talking about how to create services and timers :
> https://www.linuxtricks.fr/wiki/systemd-creer-des-services-timers-unites
>
> I hope this finally helps for you Dorian
>
>
>
>
>
>
>
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] dockerd broken docker works without It own docker image but need

[Reindl Harald]

that unbelievable nonsense in the style of "I was know this Is a systemd
problem because the engine of Apache is systemd" dates back at least two
years now.

Am 26.03.20 um 22:22 schrieb Michael Biebl:
> Am Do., 26. März 2020 um 21:43 Uhr schrieb Dorian ROSSE
> :
>>
>> Do you know the dockerd mailing list?
> 
> Don't be lazy and find that out yourself. Google (or your search
> engine of choice) is your friend.

 Weitergeleitete Nachricht 
Betreff:[systemd-devel] Apparmor and ureadhead failed to start
Datum:  Wed, 10 Jan 2018 09:35:31 +
Von:Dorian ROSSE 
An: systemd-devel@lists.freedesktop.org


Dear IT worker,

Since I have kernel 4.14.12 I have two errors

 Weitergeleitete Nachricht 
Betreff:[systemd-devel] Sudo program broken
Datum:  Fri, 12 Oct 2018 07:40:13 +
Von:Dorian ROSSE 
An: systemd-devel@lists.freedesktop.org


Hello Dear IT support,

My sudo program is broken how to repair It ?

Thank you in advance to answer my problem

Command line « su » answer « authentification Failure » and command line
« sudo -i » answer « sudo : /usr/bin/sudo must be owned by uid 0 and

 Weitergeleitete Nachricht 
Betreff:Re: [systemd-devel] ClamAV Log Errors
Datum:  Sun, 16 Sep 2018 06:52:30 +
Von:Dorian ROSSE 
An: systemd-devel@lists.freedesktop.org


Hello Dear IT SystemD Team Workers,

I have a few errors for symbolic links or empty files at the end of the
clam AV scan journal also finaly I attached a txt file which all errors
meet by clam AV,

 Weitergeleitete Nachricht 
Betreff:Re: [systemd-devel] Failed to start apache2 with error code
exited 1 failure
Datum:  Mon, 20 May 2019 09:34:38 +
Von:Dorian ROSSE 
An: Andy Pieters ,
systemd-de...@freedesktop.org 

Ok I will ask to Apache but I was know this Is a systemd problem because
the engine of Apache is systemd...

It is not bad you have take the time for explained,

Have a Nice week,

Regards.
Dorian Rosse.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Stateless system - Centos8 and overlayfs on root

[Silvio Knizek]

Am Freitag, den 27.03.2020, 10:17 -0700 schrieb Preston L. Bannister:
> Looking for a sanity check from the folk how know more of systemd than do I. 
> Not looking for someone else to solve my problem, but could use a clue.
>
> Trying to figure out how to get an overlayfs root mounted early in boot.
>
> Building an embedded system that must not store any sensitive data when 
> powered down. Found this was referred to on this list more recently as a 
> "stateless" system. (And Tobias Hunger seems to have the most to say. :) ) We 
> are using Centos8, with systemd 239. Starting point is a vanilla Centos8 
> server installation to a small (8 or 32GB) flash volume.
>
> Had the (possibly) clever notion of using an overlayfs as the root mount, 
> with a tmpfs as the upper, and the usual persistent volume as the lower. The  
> initial round of configuration and test would just be against a stock Centos8 
> install. Once fully configured and tested, would add a default boot menu item 
> to boot with root mounted as an overlayfs, with the fully configured root 
> volume as the read-only lower.
>
> Updates would be accomplished by booting from the original boot menu entry. 
> (This is slightly complicated by the fact the target systems' computers do 
> not have a console - but figure I can script altering the default boot.)
>
> Have what I think is a properly configured overlayfs root. Currently hung up 
> on getting that root mounted early enough(?) in boot. Working down a list of 
> possibilities. :)
>
> Have a script to repeatably build/rebuild the overlayfs root. Relevant 
> commands (w/o supporting logic):
> 
> BASE=/run/overlay_root
> OVERLAY=$BASE/merged
> ROOT_MOUNT=$OVERLAY/mnt/root
> mount -t tmpfs root-base $BASE ; mkdir $BASE/{lower,upper,work,merged}
> mount --bind / $BASE/lower
> mount -t overlayfs root-overlay $OVERLAY 
> -olowerdir=$BASE/lower,upperdir=$BASE/upper,workdir=$BASE/work
> for d in boot dev proc run sys ; do mount --bind /$d $OVERLAY/$d ; done
> mkdir $ROOT_MOUNT ; mount --bind / $ROOT_MOUNT
> 
> This all seems to work. The overlayfs prevents writes to persistent media in 
> usual places. Have a path to write to persistent media. The special 
> directories (that do not work from mounts to lower on an overlayfs) work as 
> expected.
>
> What I do not have as yet is a means to get the overlayfs root mounted early 
> in boot.
> 1.  Does not look like /etc/fstab can create the overlayfs.
> 2.  Tried the "systemd.volatile=yes" kernel command line, w/o luck. 
> Substantial commits between 239 and 245 around this.
> 3.  See systemd "pivot_root" and "switch_root", but not yet puzzled out usage.
>
> Looking for where/how to swap in the overlayfs root early in boot. Or tell me 
> I'm an idiot, and this will not work. :/

Hi Preston,

So, you need a initramfs doing this for you and where you do all the
mounting. Or you use tmpfiles.d snippets and /etc as tmpfs. See
http://0pointer.net/blog/projects/stateless.html for more information.

BR
Silvio

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Stateless system - Centos8 and overlayfs on root

[Preston L. Bannister]

Looking for a sanity check from the folk how know more of systemd than do
I. Not looking for someone else to solve my problem, but could use a clue.

Trying to figure out how to get an overlayfs root mounted early in boot.

Building an embedded system that must not store any sensitive data when
powered down. Found this was referred to on this list more recently as a
"stateless" system. (And Tobias Hunger seems to have the most to say. :) )
We are using Centos8, with systemd 239. Starting point is a vanilla Centos8
server installation to a small (8 or 32GB) flash volume.

Had the (possibly) clever notion of using an overlayfs as the root mount,
with a tmpfs as the upper, and the usual persistent volume as the lower.
The  initial round of configuration and test would just be against a stock
Centos8 install. Once fully configured and tested, would add a default boot
menu item to boot with root mounted as an overlayfs, with the fully
configured root volume as the read-only lower.

Updates would be accomplished by booting from the original boot menu entry.
(This is slightly complicated by the fact the target systems' computers do
not have a console - but figure I can script altering the default boot.)

Have what I think is a properly configured overlayfs root. Currently hung
up on getting that root mounted early enough(?) in boot. Working down a
list of possibilities. :)

Have a script to repeatably build/rebuild the overlayfs root. Relevant
commands (w/o supporting logic):

BASE=/run/overlay_root
OVERLAY=$BASE/merged
ROOT_MOUNT=$OVERLAY/mnt/root
mount -t tmpfs root-base $BASE ; mkdir $BASE/{lower,upper,work,merged}
mount --bind / $BASE/lower
mount -t overlayfs root-overlay $OVERLAY
-olowerdir=$BASE/lower,upperdir=$BASE/upper,workdir=$BASE/work
for d in boot dev proc run sys ; do mount --bind /$d $OVERLAY/$d ; done
mkdir $ROOT_MOUNT ; mount --bind / $ROOT_MOUNT

This all seems to work. The overlayfs prevents writes to persistent media
in usual places. Have a path to write to persistent media. The special
directories (that do not work from mounts to lower on an overlayfs) work as
expected.

What I do not have as yet is a means to get the overlayfs root mounted
early in boot.
1.  Does not look like /etc/fstab can create the overlayfs.
2.  Tried the "systemd.volatile=yes" kernel command line, w/o luck.
Substantial commits between 239 and 245 around this.
3.  See systemd "pivot_root" and "switch_root", but not yet puzzled out
usage.

Looking for where/how to swap in the overlayfs root early in boot. Or tell
me I'm an idiot, and this will not work. :/
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] dockerd broken docker works without It own docker image but need

[Juice]

Dorian ROSSE kirjoitti perjantai 27. maaliskuuta 2020:
> I was know a program who finish by "d" is a systemd program instead it real 
> name without the "d"
>

Where do you get these ideas?

  - juice -
 

-- 
Sent from my SFOS/XperiaX
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] dockerd broken docker works without It own docker image but need

[Reindl Harald]

Am 27.03.20 um 07:56 schrieb Dorian ROSSE:
> I was know a program who finish by "d" is a systemd program

i doubt that httpd, mysqld and so on are a systemd program given that
they all existed decades before
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] dockerd broken docker works without It own docker image but need

[Dorian ROSSE]

I was know a program who finish by "d" is a systemd program instead it real 
name without the "d"

I have found docker sig and docker Google group,

I don't know what choose,

I will try to share my problem on the docker Google group,

Finaly I leave again the mailing list,

Regards.


Dorian Rosse.

Téléchargez Outlook pour Android

From: Peter Hoeg 
Sent: Friday, March 27, 2020 1:59:28 AM
To: Dorian ROSSE 
Subject: Re: [systemd-devel] dockerd broken docker works without It own docker 
image but need

Come on man, we talked about this *just* yesterday.

The systemd mailing list is *not* for any of this. Do you understand that?

--
Regards,
Peter
On 20-03-26 at 17:41, Dorian ROSSE wrote:
>   Hello,
>   dockerd is broken,
>   docker works without It own docker image but I need,
>   when I run 'docker network list' It shows docker image but nothing in the
>   docker container fedora window...
>   I have run this :
>   'grubby --update-kernel=ALL --args="systemd.unified_cgroup_hierarchy=0'
>   then I have reboot since this command line and the reboot dockerd is
>   broken this next command line show the docker status :
>   'dockerd -D -p /var/run/docker.pid'
>   I happen error :
>   pid file found ensure docker is not running or delete /var/run/docker.pid
>   Thank you in advance to help myself run docker image,
>   Regards.
>   Dorian ROSSE.

>___
>systemd-devel mailing list
>systemd-devel@lists.freedesktop.org
>https://lists.freedesktop.org/mailman/listinfo/systemd-devel
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel