[systemd-devel] fully volatile running from ram
hello, in a fully-volatile boot scenario /usr from a physical disk gets mounted on top of an instance of a tmpfs. my first question is why is that necessary? (the tmpfs part i mean) my second question is, would it be possible to do the same but rather than mounting the /usr *populate* the said tmpfs with OS tree from said physical disk, preferably in a blocked or fs cached setup (db-cache or bcachefs). i realise that this can be done easily in initrd or even initramfs can hold the /usr but the problem there is when we boot "developmen" and not "production" in which case we want updates to be written to disk. jrun ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] fully volatile running from ram
On Wed, Apr 26, 2017 at 04:08:21PM +0200, Lennart Poettering wrote: > On Tue, 25.04.17 13:13, jr (darwinsker...@gmail.com) wrote: > > > hello, > > > > in a fully-volatile boot scenario /usr from a physical disk gets mounted on > > top of an instance of a tmpfs. my first question is why is that necessary? > > (the tmpfs part i mean) > > I am not sure I grok what you are trying to say? tmpfs is how on Linux > you can easily have a volatile file system, as it lives entirely in > memory and never hits the disk (admittedly modulo swapping). > but once you mount over that tmpfs from disk the overlaying fs will hide the underlying tmpfs, no? baring the fs-caching done in kernel (readahead?), for anything that needs to be loaded into memory for executing or otherwise disk has to be touched for, well reading, at least once, no? this is the part i'm trying to understand, if the overlaying fs is mounted from physical disk, does mounting over tmpfs causes kernel to cache that fs entirely into memory? this looks a lot like initramfs where it is an instance of tmpfs but that also gets *shadowed* once "real_root" is switched to, no? > > my second question is, would it be possible to do the same but rather > > than mounting the /usr *populate* the said tmpfs with OS tree from said > > physical disk, preferably in a blocked or fs cached setup (db-cache or > > bcachefs). i realise that this can be done easily in initrd or even > > initramfs can hold the /usr but the problem there is when we boot > > "developmen" and not "production" in which case we want updates to be > > written to disk. > > I am not grokking this question either, but keeping the whole OS in > memory of course means you need a lot of memory. Moreover depending on > disk speeds it means your boot will be quite slow, as you copy stuff over > every single time before you can boot. If you copy things around like > that during boot the best thing would be to do it in the initrd, as > otherwise you are running the system already, that you are about to > prepare for running, and dropping open references the the old files is > hard (though not entirely impossible, after all there is "systemctl > daemon-reexec" and things). no, no, i'm thinking systemd as rdinit rather than init; i.e. initramfs is the real_root. one way of doing it is to pack the /usr into a initramfs archive and either build it into kernel or pass it via bootload (never worked for me)? then you boot the system into ram, enjoy blazing fast responsiveness of it but there comes along some update that one would like to apply and it turns out be really great that update. but how do you make it stick then? in fact if /var is not volatile and your package manager keeps it's records there (in my case portage does) on the next boot system is confused because it thinks that updates are going to be there. this has a number of solutions; bcachefs or dm-cache or even --overlay. --overlay is cool since it stages the upgrade; caching solutions are for performance though. i just don't know if the hooks are there (kernel and/or systmd) too boot the system this way? i.e. populate the initramfs from current or next or the one-after gold-master which resides on disk; start working on initramfs; associate this initramfs with original or another block-device or subvol of an fs on the disk and let our chosen caching system take care of mirroring our working tree with said *backup*. next reboot we should have the option of roll-back or continuing with our work and so on. please, please let me know if i'm still making no-sense :) English is not my strong suit and on top of that i'm horrible at explaining something. jrun ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd - nspawn ; systemd-networkd ; containers
Greetings - I hope this finds you well and that I provide a set of good starting details ... I have been using systemd-nspawn to create 'containers'/machines that I use on hosts. These machines were set up with unique IP addresses so I have multiple machines on same host (in some cases sharing the host network and in some cases using a secondary ethernet). ... Recently I updated one of my hosts to F30 and went to create a new machine. The main thrust of this email is that in my process of creating a new systemd-nspawn machine it seems that `systemd-networkd` is not installed when I use my steps (I can outline if that will help) to create a machine. So, in turn I am not able to set up the machine with unique network configuration at this point. I have running systems with systemd v219 (potentially too old, sorry) and v229 that have machines (systemd-nspawn containers) networked. At this point I was looking to bring up a new sytemd-nspawn container/machine on a host that has v241. specifically : ==> systemd 241 (v241-12.git1e19bcd.fc30) +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid When I follow (my) steps/process for creating a new systemd-nspawn, I get this response ==> 'No match for argument: systemd-networkd'. So, I have few starting questions and I can provide more details as needed/requested 1) Has there been, since v219 or v229 a change (that I have yet to uncover the details) that have moved from systemd-networkd to something new/different/better? What is that Or what should I be installing instead of systemd-networkd? 2) Can you direct me to the details about how to migrate from 'systemd-networkd'? 3) This is a bit of an open point --- Should I use systemd-nspawn machines to run resources? Is there another suggested path I should educate myself on for having containers (podman? )? I built up my process for bringing up machines and found that very useful/powerful to have containers running on a host that I can have as unique machines (IP addresses, and processes etc.). Have I over-used the technology OR is it safe/suggested to use nspawn in this manner? Later I will look to create more machines on Centos8 (systemctl --version ==>239). Let me know if I can add more details Or if I need to be more specific. Thanks in advance for your time. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd - nspawn ; systemd-networkd ; containers
I get the error when, on the host, I am creating the container. To this point, I have found my setups work needing systemd-networkd on both the host and container. The distro for the container I am working to set up is 'Fedora 30 '. That is also the host distro too. Seems I have something wrong on my side. Thanks for your help/time. What else can I provide that will aid in isolating this? I have running CentOS 7 and Fedora 29 hosts that have a mix of fedora and centos containers running with their own unique IPs and the goal ==> migrate to Fedora30 and CentOS8 //From notes I have captured for my setup: //must run systemd-networkd systemd-networkd is a system daemon that manages network configurations. It detects and configures network devices as they appear; it can also create virtual network devices. This service can be especially useful to set up complex network configurations for a container managed by systemd-nspawn or for virtual machines. It also works fine on simple connections. On Fri, Sep 27, 2019 at 10:31 PM Ryan Gonzalez wrote: > I'm a bit confused, where is the error about networkd not being found > coming from? Do you want networkd on the host system or inside the > container? If the latter, what distro does the container run? > > On Fri, Sep 27, 2019, 6:57 PM Douglas E. Hopley Jr. > wrote: > >> Greetings - I hope this finds you well and that I provide a set of good >> starting details ... >> >> I have been using systemd-nspawn to create 'containers'/machines that I >> use on hosts. These machines were set up with unique IP addresses so I >> have multiple machines on same host (in some cases sharing the host network >> and in some cases using a secondary ethernet). ... >> >> Recently I updated one of my hosts to F30 and went to create a new >> machine. >> >> The main thrust of this email is that in my process of creating a new >> systemd-nspawn machine it seems that `systemd-networkd` is not installed >> when I use my steps (I can outline if that will help) to create a machine. >> So, in turn I am not able to set up the machine with unique network >> configuration at this point. >> >> I have running systems with systemd v219 (potentially too old, sorry) >> and v229 >> that have machines (systemd-nspawn containers) networked. >> >> At this point I was looking to bring up a new sytemd-nspawn >> container/machine on a host that has v241. specifically : >> ==> >> systemd 241 (v241-12.git1e19bcd.fc30) >> +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP >> +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN >> +PCRE2 default-hierarchy=hybrid >> >> When I follow (my) steps/process for creating a new systemd-nspawn, I >> get this response ==> 'No match for argument: systemd-networkd'. >> >> So, I have few starting questions and I can provide more details as >> needed/requested >> >> 1) Has there been, since v219 or v229 a change (that I have yet to >> uncover the details) that have moved from systemd-networkd to something >> new/different/better? What is that Or what should I be installing instead >> of systemd-networkd? >> >> 2) Can you direct me to the details about how to migrate from >> 'systemd-networkd'? >> >> >> 3) This is a bit of an open point --- Should I use systemd-nspawn >> machines to run resources? Is there another suggested path I should >> educate myself on for having containers (podman? )? I built up my process >> for bringing up machines and found that very useful/powerful to have >> containers running on a host that I can have as unique machines (IP >> addresses, and processes etc.). Have I over-used the technology OR is it >> safe/suggested to use nspawn in this manner? >> >> Later I will look to create more machines on Centos8 (systemctl --version >> ==>239). >> >> Let me know if I can add more details Or if I need to be more specific. >> >> Thanks in advance for your time. >> >> >> ___ >> systemd-devel mailing list >> systemd-devel@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/systemd-devel > > -- Douglas E. Hopley Jr. email = hop...@ipcloud.net url = ipcloud.net ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd - nspawn ; systemd-networkd ; containers
Two things :
1) I used the following on the host (you noted I do not need
systemd-networkd on the host)
# dnf install systemd-networkd
==>
No match for argument: systemd-networkd
Error: Unable to find a match: systemd-networkd
2) To create the container (feedback welcome) I used :
//
export RELVER=30
dnf -y --nogpg --releasever=${RELVER} --installroot=/var/lib/machines/nh286
install systemd systemd-networkd passwd dnf vim-minimal iputils iproute
procps-ng vim-enhanced
==> ...
No match for argument: systemd-networkd
Error: Unable to find a match: systemd-networkd
NOTE: the dnf command I have used previously for other container
builds/creation on other hosts
On Sat, Sep 28, 2019 at 10:11 AM Ryan Gonzalez wrote:
> Hmm that's odd, Fedora should have systemd-networkd by default, and you
> shouldn't need it on the host (I've used networkd on the container end
> before but always use NetworkManager on my host system.) What command
> *exactly* gave the error that networkd wasn't found?
>
> On Sat, Sep 28, 2019, 11:03 AM Douglas E. Hopley Jr.
> wrote:
>
>> I get the error when, on the host, I am creating the container.
>>
>> To this point, I have found my setups work needing systemd-networkd on
>> both the host and container.
>>
>> The distro for the container I am working to set up is 'Fedora 30 '.
>> That is also
>> the host distro too. Seems I have something wrong on my side.
>>
>> Thanks for your help/time. What else can I provide that will aid in
>> isolating this?
>>
>>
>>
>> I have running CentOS 7 and Fedora 29 hosts that have a mix of fedora
>> and centos containers
>> running with their own unique IPs and the goal ==> migrate to Fedora30
>> and CentOS8
>>
>> //From notes I have captured for my setup:
>> //must run systemd-networkd
>> systemd-networkd is a system daemon that manages network configurations.
>> It detects and configures network devices as they appear; it can also
>> create virtual network devices. This service can be especially useful
>> to set up complex network configurations for a container managed by
>> systemd-nspawn or for virtual machines. It also works fine on simple
>> connections.
>>
>>
>> On Fri, Sep 27, 2019 at 10:31 PM Ryan Gonzalez wrote:
>>
>>> I'm a bit confused, where is the error about networkd not being found
>>> coming from? Do you want networkd on the host system or inside the
>>> container? If the latter, what distro does the container run?
>>>
>>> On Fri, Sep 27, 2019, 6:57 PM Douglas E. Hopley Jr. <
>>> hop...@f6systems.com> wrote:
>>>
>>>> Greetings - I hope this finds you well and that I provide a set of
>>>> good starting details ...
>>>>
>>>> I have been using systemd-nspawn to create 'containers'/machines that I
>>>> use on hosts. These machines were set up with unique IP addresses so I
>>>> have multiple machines on same host (in some cases sharing the host network
>>>> and in some cases using a secondary ethernet). ...
>>>>
>>>> Recently I updated one of my hosts to F30 and went to create a new
>>>> machine.
>>>>
>>>> The main thrust of this email is that in my process of creating a new
>>>> systemd-nspawn machine it seems that `systemd-networkd` is not installed
>>>> when I use my steps (I can outline if that will help) to create a machine.
>>>> So, in turn I am not able to set up the machine with unique network
>>>> configuration at this point.
>>>>
>>>> I have running systems with systemd v219 (potentially too old, sorry)
>>>> and v229
>>>> that have machines (systemd-nspawn containers) networked.
>>>>
>>>> At this point I was looking to bring up a new sytemd-nspawn
>>>> container/machine on a host that has v241. specifically :
>>>> ==>
>>>> systemd 241 (v241-12.git1e19bcd.fc30)
>>>> +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP
>>>> +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS
>>>> +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid
>>>>
>>>> When I follow (my) steps/process for creating a new systemd-nspawn, I
>>>> get this response ==> 'No match for argument: systemd-networkd'.
>>>>
>>>> So, I have few starting questions and I can provide more details as
>>>> needed/requested
>>>>
>>>> 1) Has there been, s
[systemd-devel] portable services v239
Greetings. I would like to work with portable services and have a bootstrapping question. thanks in advance for your time What is the recommended/preferred distro to use to stay on the latest? Currently my F29 has : systemctl --version systemd 238 +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid How would/could I create new machine that would have v239? Doug ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] portable services v239
Got it. Thanks Ryan. I have a machine ready for this and I will do an updated install (F29). I will update/confirm back here. Thanks for your feedback Doug On Tue, Aug 28, 2018 at 8:33 PM, Ryan Gonzalez wrote: > Fedora 29 should have 239, so I'm not sure how you're on 238... > > That being said, pretty much any rolling release distro (e.g. Arch) should > have 239 by now. > > On Tue, Aug 28, 2018, 9:15 PM Douglas E. Hopley Jr. > wrote: > >> Greetings. >> >> I would like to work with portable services and have a bootstrapping >> question. >> >> thanks in advance for your time >> >> >> What is the recommended/preferred distro to use to stay on the latest? >> Currently my >> F29 has : >> >> systemctl --version >> systemd 238 >> +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP >> +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN >> +PCRE2 default-hierarchy=hybrid >> >> >> How would/could I create new machine that would have v239? >> >> Doug >> >> ___ >> systemd-devel mailing list >> systemd-devel@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/systemd-devel >> > -- > > Ryan (ライアン) > Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else > https://refi64.com/ > -- <http://ipcloud.net> ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
