Announcement

Collapse
No announcement yet.

Systemd-Import Expands Its Container Capabilities

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Systemd-Import Expands Its Container Capabilities

    Phoronix: Systemd-Import Expands Its Container Capabilities

    The systemd-import command is now more powerful after the latest batch of changes committed by Lennart Poettering prior to starting the weekend...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2


    what is this crap?

    Comment


    • #3
      Code:
        These changes will be found with the upcoming systemd 217 release.
      217 has been out for awhile, you might wanna change that to 219

      Comment


      • #4
        Originally posted by pheldens View Post


        what is this crap?
        something you don't understand cuz its computer stuff

        Comment


        • #5
          Originally posted by pheldens View Post


          what is this crap?
          An attempt at creating a simple, standard, convenient method for importing (Docker) container images to your linux host running systemd?

          Originally posted by Lennart Poettering (G+ post)
          Here's a small, but powerful new tool I added to +systemd today: "systemd-import" can pull and update container images from the Internet, in the format and via the APIs of today's best known Linux container solution. This lightweight tool downloads the images, converts them into btrfs subvolumes/snapshots and makes them available as simple directory trees in /var/lib/container/, like any other container tree, which you then can boot with "systemd-nspawn".

          This how you use it:

          Code:
          # systemd-import pull-dkr mattdm/fedora
          # systemd-nspawn -M fedora
          This first downloads "mattdm/fedora", and installs it into /var/lib/container/fedora, and then boots it directly via systemd-nspawn, like any other container tree.

          All this with only a bit of C code, as part of the systemd suite. No new dependencies. No Go, no Python, no other runtime.

          Next: add support for non-btrfs systems for this (by transparently creating a dynamically sized loopback file somewhere in /var, with btrfs inside, which can be used for this, so that only the redundant container images can reside in it, but your private user data and the rest of the OS don't have to be entrusted to btrfs).

          Enjoy!

          (link to original post)

          Comment


          • #6
            Since systemd is best click-bait, soon we will have an article for every commit

            Comment


            • #7
              Originally posted by magika View Post
              Since systemd is best click-bait, soon we will have an article for every commit
              What we need right now is an article about this typo being corrected from "see" to "sse" http://cgit.freedesktop.org/systemd/...b9bc624e7bfe3f

              Comment


              • #8
                Originally posted by halo9en View Post
                What we need right now is an article about this typo being corrected from "see" to "sse" http://cgit.freedesktop.org/systemd/...b9bc624e7bfe3f

                BLOAT!

                Comment


                • #9
                  With the way Poettering is going, systemd will soon control all major system functions and making the Linux kernel act more like a microkernel

                  I think that's what he wants...total control!

                  Comment


                  • #10
                    You people do not even fucking read what the change is, do you? "Systemd in the title?! Hold my beard, I have to type an angry forum post!"

                    Comment

                    Working...
                    X