meta-virtualization.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Freihofer <adrian.freihofer@gmail.com>
To: meta-virtualization@lists.yoctoproject.org
Cc: Adrian Freihofer <adrian.freihofer@siemens.com>
Subject: [meta-virtualization][PATCH 0/5] docker update to 23.0.6
Date: Mon, 15 May 2023 17:26:19 +0200	[thread overview]
Message-ID: <20230515152624.138713-1-adrian.freihofer@siemens.com> (raw)

Tested using the following layers:
- poky LTS, branch = kirkstone
- meta-lts-mixins, branch = kirkstone/go
- meta-lts-mixins, branch = kirkstone/rust
- meta-virtualization, branch = master

To one of my layers.conf files I added a hack:
  LAYERSERIES_COMPAT_virtualization-layer += "kirkstone"
Otherwise the mixin layers seams to work surpisingly well with
meta-virtualization master branch, at least for Docker.

From target device:

docker info
    Client:
    Context:    default
    Debug Mode: false

    Server:
    Containers: 0
      Running: 0
      Paused: 0
      Stopped: 0
    Images: 0
    Server Version: 23.0.6
    Storage Driver: overlay2
      Backing Filesystem: extfs
      Supports d_type: true
      Using metacopy: false
      Native Overlay Diff: true
      userxattr: false
    Logging Driver: journald
    Cgroup Driver: systemd
    Cgroup Version: 2
    Plugins:
      Volume: local
      Network: bridge host ipvlan macvlan null overlay
      Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
    Swarm: active
      NodeID: 2e9d3m5f67wpovhnnttnj763z
      Is Manager: true
      ClusterID: ivh4ga9xrsu9js9ah6se8pg5n
      Managers: 1
      Nodes: 1
      Default Address Pool: 10.0.0.0/8  
      SubnetSize: 24
      Data Path Port: 4789
      Orchestration:
      Task History Retention Limit: 1
      Raft:
      Snapshot Interval: 10000
      Number of Old Snapshots to Retain: 0
      Heartbeat Tick: 1
      Election Tick: 10
      Dispatcher:
      Heartbeat Period: 5 seconds
      CA Configuration:
      Expiry Duration: 3 months
      Force Rotate: 0
      Autolock Managers: false
      Root Rotation In Progress: false
      Node Address: 192.168...
      Manager Addresses:
      192.168...:2377
    Runtimes: io.containerd.runc.v2 runc
    Default Runtime: runc
    Init Binary: docker-init
    containerd version: 1677a17964311325ed1c31e2c0a3589ce6d5c30d.m
    runc version: v1.1.7-0-g860f061b-dirty
    init version: b9f42a0-dirty
    Security Options:
      seccomp
      Profile: builtin
      cgroupns
    Kernel Version: 5.15.71+gitb280d94
    Operating System: My Distro
    OSType: linux
    Architecture: aarch64
    CPUs: 2
    Total Memory: 1.784GiB
    Name: my-host
    ID: 612ad6f3-0694-4252-befe-fcfb1f804bdc
    Docker Root Dir: /data/lib/docker
    Debug Mode: false
    Registry: https://index.docker.io/v1/
    Experimental: false
    Insecure Registries:
      127.0.0.0/8
    Live Restore Enabled: false


docker run -it alpine /bin/sh
    Unable to find image 'alpine:latest' locally
    latest: Pulling from library/alpine
    08409d417260: Pull complete 
    Digest: sha256:02bb6f428431fbc2809c5d1b41eab5a68350194fb508869a33cb1af4444c9b11
    Status: Downloaded newer image for alpine:latest
    / # cat /etc/os-release 
    NAME="Alpine Linux"
    ID=alpine
    VERSION_ID=3.18.0
    PRETTY_NAME="Alpine Linux v3.18"
    HOME_URL="https://alpinelinux.org/"
    BUG_REPORT_URL="https://gitlab.alpinelinux.org/alpine/aports/-/issues"
    / # exit


docker run -it debian /bin/bash
    Unable to find image 'debian:latest' locally
    latest: Pulling from library/debian
    d677c78be691: Pull complete 
    Digest: sha256:63d62ae233b588d6b426b7b072d79d1306bfd02a72bff1fc045b8511cc89ee09
    Status: Downloaded newer image for debian:latest
    root@84f1d770edfd:/# cat /etc/os-release 
    PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
    NAME="Debian GNU/Linux"
    VERSION_ID="11"
    VERSION="11 (bullseye)"
    VERSION_CODENAME=bullseye
    ID=debian
    HOME_URL="https://www.debian.org/"
    SUPPORT_URL="https://www.debian.org/support"
    BUG_REPORT_URL="https://bugs.debian.org/"
    root@84f1d770edfd:/# exit
    exit

Adrian Freihofer (5):
  busybox-initrd: auto pv from busybox
  containerd: update to 1.7.1
  moby: update to v23.0.6
  runc-opencontainers: update to 1.1.7
  runc-docker: update to 1.1.7

 .../containerd/containerd-opencontainers_git.bb    |  6 +++---
 recipes-containers/docker/docker-moby_git.bb       |  8 ++++----
 recipes-containers/runc/runc-docker_git.bb         |  4 ++--
 recipes-containers/runc/runc-opencontainers_git.bb |  4 ++--
 ...{busybox-initrd_1.36.0.bb => busybox-initrd.bb} | 14 ++++++++++++++
 5 files changed, 25 insertions(+), 11 deletions(-)
 rename recipes-core/busybox/{busybox-initrd_1.36.0.bb => busybox-initrd.bb} (59%)

-- 
2.40.1



             reply	other threads:[~2023-05-15 15:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 15:26 Adrian Freihofer [this message]
2023-05-15 15:26 ` [meta-virtualization][PATCH 1/5] busybox-initrd: auto pv from busybox Adrian Freihofer
2023-05-17 15:51   ` Bruce Ashfield
2023-05-15 15:26 ` [meta-virtualization][PATCH 2/5] containerd: update to 1.7.1 Adrian Freihofer
2023-05-15 15:26 ` [meta-virtualization][PATCH 3/5] moby: update to v23.0.6 Adrian Freihofer
2023-05-15 15:26 ` [meta-virtualization][PATCH 4/5] runc-opencontainers: update to 1.1.7 Adrian Freihofer
2023-05-15 15:26 ` [meta-virtualization][PATCH 5/5] runc-docker: " Adrian Freihofer
2023-07-26  9:46   ` Martin Jansa
2023-07-26 13:23     ` Bruce Ashfield
2023-07-26 13:34       ` Martin Jansa
2023-05-15 15:59 ` [meta-virtualization][PATCH 0/5] docker update to 23.0.6 Bruce Ashfield

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230515152624.138713-1-adrian.freihofer@siemens.com \
    --to=adrian.freihofer@gmail.com \
    --cc=adrian.freihofer@siemens.com \
    --cc=meta-virtualization@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).