General Availability of containerd 1.0 is Here!

  • Today, we:undefined:’:undefined:re pleased to announce that containerd (pronounced Con-Tay-Ner-D), an industry-standard runtime for building container solutions, has reached its 1.0 milestone. FromDocker:undefined:’:undefined:s announcement in December of last year that it was spinning out its core runtime toits donation to the CNCF in March 2017, the containerd project has experienced significant growth and progress over the past 12 months. Within both the Docker and Kubernetes communities, there has been a significant uptick in investment with contributions from independents and CNCF member companies alike including Docker, Google, NTT, IBM, Microsoft, AWS, ZTE, Huawei and ZJU.

    Similarly, the maintainers have been working to add key functionality to containerd. The initial containerd donation included methods for:

    • transferring container images,
    • container execution and supervision,
    • low-level local storage and network interfaces and
    • the ability to work on both Linux, Windows and other platforms.

    Additional work has been done to add a:

    • complete storage and distribution system that supports both OCI and Docker image formats and
    • robust events system
    • A more sophisticated snapshot model to manage container filesystems

    These changes helped the team build out a smaller interface for the snapshotters, while still fulfilling the requirements needed from things like a builder. It also reduces the amount of code needed, making it much easier to maintain in the long run.

    The containerd 1.0 milestone comes after several months of in alpha and beta status, that allowed the team to implement many performance improvements: creation of a stress testing system, improvements in garbage collection and shim memory usage.

    :undefined:“:undefined:In 2017 key functionality has been added containerd to address the needs of modern container platforms like Docker and orchestration systems like Kubernetes,:undefined:”:undefined: said Michael Crosby, Maintainer for containerd and engineer at Docker. :undefined:“:undefined:Since our announcement in December, we have been progressing the design of the project with the goal of making it easily embeddable in higher level systems to provide core container capabilities. We will continue to work with the community to create a runtime that:undefined:’:undefined:s lightweight yet powerful, balancing new functionality with the desire for code that is easy to support and maintain.:undefined:”:undefined:

    containerd is already being used by Kubernetes for itscri-containerd project, which enables users to run Kubernetes clusters using containerd as the underlying runtime. containerd is also an essential upstream component of the Docker platform and is currently used by millions of end users. There is also strong alignment with other CNCF projects: containerd exposes an API usinggRPC and exposes metrics in thePrometheus format. containerd also fully leverages the Open Container Initiative (OCI) runtime, image format specifications and OCI reference implementation (runC), and will pursue OCI certification when it is available.

    Key Milestones in the progress to 1.0 include:

    Notable containerd facts and figures:

    • 1922 GitHub stars, 401 forks
    • 108 contributors
    • 8 maintainers from independents and and member companies alike including Docker, Google, IBM, ZTE and ZJU .
    • 2949+ commits, 26 releases

    Availability and Resources

    To participate in containerd: .

    Meet us at KubeCon

    Learn more about containerd at KubeCon by attending Justin Cormack:undefined:’:undefined:sLinuxKit & Kubernetes talk at Austin Docker Meetup, Patrick Chanezon:undefined:’:undefined:sMoby session Phil Estes:undefined:’:undefined: session or thecontainerd salon<u>.</u>

    The postGeneral Availability of containerd 1.0 is Here! appeared first onThe Linux Foundation.

  • Make ISO from DVD

    In this case I had an OS install disk which was required to be on a virtual node with no optical drive, so I needed to transfer an image to the server to create a VM

    Find out which device the DVD is:



    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 464.8G 0 part ├─centos-root 253:0 0 50G 0 lvm / ├─centos-swap 253:1 0 11.8G 0 lvm [SWAP] └─centos-home 253:2 0 403G 0 lvm /home sdb 8:16 1 14.5G 0 disk /mnt sr0 11:0 1 4.1G 0 rom /run/media/rick/CCSA_X64FRE_EN-US_DV5

    Therefore /dev/sr0 is the location , or disk to be made into an ISO

    I prefer simplicity, and sometimes deal with the fallout after the fact, however Ive repeated this countless times with success.

    dd if=/dev/sr0 of=win10.iso

    Where if=Input file and of=output file

    I chill out and do something else while the image is being copied/created, and the final output:

    8555456+0 records in 8555456+0 records out 4380393472 bytes (4.4 GB) copied, 331.937 s, 13.2 MB/s


    read more
  • Recreate postrgresql database template encode to ASCII

    UPDATE pg_database SET datistemplate = FALSE WHERE datname = 'template1';

    Now we can drop it:

    DROP DATABASE template1;

    Create database from template0, with a new default encoding:

    CREATE DATABASE template1 WITH TEMPLATE = template0 ENCODING = 'UNICODE'; UPDATE pg_database SET datistemplate = TRUE WHERE datname = 'template1'; \c template1 VACUUM FREEZE;

    read more