Message ID | 20210329155640.62445-1-silvano.cirujano-cuesta@siemens.com |
---|---|
Headers | show |
Series | Add support for containerized root filesystems | expand |
29.03.2021 18:56, Silvano Cirujano Cuesta wrote: > v8: cosmetic changes in docs and small fix in CI script > > v7: issues in sample configurations and CI script fixed and tested on > two different CI environments. > > This patch series provides support for containerized root filesystems, > for both target images and SDKs. > > For containerized target images the new image type `container-img` has > been added. > > For containerized SDKs the task `populate_sdk` has been extended. > > Containerized root filesystems are easy to distribute and run, enabling > this way following scenarios: > - Use ISAR to build container images meant to be run only in containers. > - Use the same ISAR configuration to build images for containers, VMs > and bare-metal. > - Easy SDK distribution and "installation". > - Quickly testing certain applications in the workstation using the > target root filesystem. > > In order to build containerized target root filesystems `IMAGE_TYPE` has > to be `container-img`, additionally the container image format can be > selected with the variable `CONTAINER_FORMATS`. The default format is > `docker-archive`. > > In order to build containerized SDKs the variable `SDK_FORMAT` has to > provide any of the supported container formats (e.g. `docker-archive`). > The default format is the legacy non-containerized: `tar_xz`. > > It also provides a sample machine, multiconfigs and ci-testing. > > More information about its usage is documented in the file > docs/user_manual.md. > > A PoC/demo of this functionality (only the SDK part) has been created > based on the project https://github.com/siemens/meta-iot2050. > Jan Kiszka already tested and liked it! => > https://github.com/siemens/meta-iot2050/issues/86#issuecomment-768907845 > > Successful builds of both containerized target and SDK are available on > the same PoC project: > - https://github.com/Silvanoc/meta-iot2050/actions/runs/558311580 > - https://github.com/Silvanoc/meta-iot2050/actions/runs/558311581 > and also the resulting images: > - https://github.com/users/Silvanoc/packages/container/package/meta-iot2050%2Fiot2050-debian-arm64 > - https://github.com/users/Silvanoc/packages/container/package/meta-iot2050%2Fiot2050-debian-sdk-arm64 > > In order to get a feeling about its usage (you need Docker or Podman), > follow these simple copy&paste instructions: > https://github.com/Silvanoc/meta-iot2050/blob/master/kas/BUILDING-SDK-CONTAINER.md#running-the-sdk > Build instructions are available in the upper part of that document. > > Two new dependencies (umoci and skopeo -backporting from bullseye to > buster works easily) are required to create containerized root > filesystems (as specified in the documentation). > > Typical container image management actions (e.g. push an image to a > container image regitry) are out of scope. Available tools (Docker, > Skopeo, Buildah, Podman,...) should be used for these actions. > > A patch will follow this one to get the dependencies into the container > images being provided by the project > https://github.com/siemens/kas (for `kas-container`, for example). > > Silvano Cirujano Cuesta (5): > classes: add root filesystem containerizing class > classes: add new image type 'container-img' > sdk: add support for containerized sdk > docs: document creation of container images > ci: add container image sample configurations > > doc/user_manual.md | 179 ++++++++++++++++++ > meta-isar/conf/local.conf.sample | 3 + > meta-isar/conf/machine/container.conf | 5 + > .../conf/multiconfig/container-bullseye.conf | 4 + > .../conf/multiconfig/container-buster.conf | 4 + > .../conf/multiconfig/container-stretch.conf | 4 + > meta/classes/container-img.bbclass | 18 ++ > .../classes/image-container-extension.bbclass | 82 ++++++++ > meta/classes/image-sdk-extension.bbclass | 42 +++- > meta/classes/image.bbclass | 1 + > scripts/ci_build.sh | 29 ++- > 11 files changed, 363 insertions(+), 8 deletions(-) > create mode 100644 meta-isar/conf/machine/container.conf > create mode 100644 meta-isar/conf/multiconfig/container-bullseye.conf > create mode 100644 meta-isar/conf/multiconfig/container-buster.conf > create mode 100644 meta-isar/conf/multiconfig/container-stretch.conf > create mode 100644 meta/classes/container-img.bbclass > create mode 100644 meta/classes/image-container-extension.bbclass > Applied to next, thanks.
On 02/04/2021 17:18, Anton Mikanovich wrote: > 29.03.2021 18:56, Silvano Cirujano Cuesta wrote: >> v8: cosmetic changes in docs and small fix in CI script >> >> v7: issues in sample configurations and CI script fixed and tested on >> two different CI environments. >> >> This patch series provides support for containerized root filesystems, >> for both target images and SDKs. >> >> For containerized target images the new image type `container-img` has >> been added. >> >> For containerized SDKs the task `populate_sdk` has been extended. >> >> Containerized root filesystems are easy to distribute and run, enabling >> this way following scenarios: >> - Use ISAR to build container images meant to be run only in containers. >> - Use the same ISAR configuration to build images for containers, VMs >> and bare-metal. >> - Easy SDK distribution and "installation". >> - Quickly testing certain applications in the workstation using the >> target root filesystem. >> >> In order to build containerized target root filesystems `IMAGE_TYPE` has >> to be `container-img`, additionally the container image format can be >> selected with the variable `CONTAINER_FORMATS`. The default format is >> `docker-archive`. >> >> In order to build containerized SDKs the variable `SDK_FORMAT` has to >> provide any of the supported container formats (e.g. `docker-archive`). >> The default format is the legacy non-containerized: `tar_xz`. >> >> It also provides a sample machine, multiconfigs and ci-testing. >> >> More information about its usage is documented in the file >> docs/user_manual.md. >> >> A PoC/demo of this functionality (only the SDK part) has been created >> based on the project https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsiemens%2Fmeta-iot2050&data=04%7C01%7Csilvano.cirujano-cuesta%40siemens.com%7C0eb5495ba8304b61405c08d8f5eaa010%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637529735344476107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Qn7AC217uocq9S2VK9b6ifhy3KO8KfIO%2F8kFpvUaLQU%3D&reserved=0. >> Jan Kiszka already tested and liked it! => >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsiemens%2Fmeta-iot2050%2Fissues%2F86%23issuecomment-768907845&data=04%7C01%7Csilvano.cirujano-cuesta%40siemens.com%7C0eb5495ba8304b61405c08d8f5eaa010%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637529735344476107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=L6Yj0Oenvr4jHAoiBOwAcNSK9na45Jg5cijDjEXwYbM%3D&reserved=0 >> >> Successful builds of both containerized target and SDK are available on >> the same PoC project: >> - https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSilvanoc%2Fmeta-iot2050%2Factions%2Fruns%2F558311580&data=04%7C01%7Csilvano.cirujano-cuesta%40siemens.com%7C0eb5495ba8304b61405c08d8f5eaa010%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637529735344476107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Z55KmOGcG3%2Fd3eNjvekAPFMma0rYQ6nJzUMkj5lFKUA%3D&reserved=0 >> - https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSilvanoc%2Fmeta-iot2050%2Factions%2Fruns%2F558311581&data=04%7C01%7Csilvano.cirujano-cuesta%40siemens.com%7C0eb5495ba8304b61405c08d8f5eaa010%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637529735344476107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ftwBFlyfCsU0ONIb%2BqF%2B%2FGfbo5Ch0orp2EV1s1HA5W4%3D&reserved=0 >> and also the resulting images: >> - https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fusers%2FSilvanoc%2Fpackages%2Fcontainer%2Fpackage%2Fmeta-iot2050%252Fiot2050-debian-arm64&data=04%7C01%7Csilvano.cirujano-cuesta%40siemens.com%7C0eb5495ba8304b61405c08d8f5eaa010%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637529735344476107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=HAcPrba0iJRZNKCVCVMllvlOZWlPH4mIKJ1%2FkDGiM7I%3D&reserved=0 >> - https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fusers%2FSilvanoc%2Fpackages%2Fcontainer%2Fpackage%2Fmeta-iot2050%252Fiot2050-debian-sdk-arm64&data=04%7C01%7Csilvano.cirujano-cuesta%40siemens.com%7C0eb5495ba8304b61405c08d8f5eaa010%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637529735344476107%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=7qKBrGsnTSrcD%2BEPEx88ZG%2FYzyxie7eXzVnzst%2B5qbQ%3D&reserved=0 >> >> In order to get a feeling about its usage (you need Docker or Podman), >> follow these simple copy&paste instructions: >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSilvanoc%2Fmeta-iot2050%2Fblob%2Fmaster%2Fkas%2FBUILDING-SDK-CONTAINER.md%23running-the-sdk&data=04%7C01%7Csilvano.cirujano-cuesta%40siemens.com%7C0eb5495ba8304b61405c08d8f5eaa010%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637529735344486101%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=v%2BYo4Y%2F317MnncO5jWxFRtlIt2JVE4kSJmR5sJhpROg%3D&reserved=0 >> Build instructions are available in the upper part of that document. >> >> Two new dependencies (umoci and skopeo -backporting from bullseye to >> buster works easily) are required to create containerized root >> filesystems (as specified in the documentation). >> >> Typical container image management actions (e.g. push an image to a >> container image regitry) are out of scope. Available tools (Docker, >> Skopeo, Buildah, Podman,...) should be used for these actions. >> >> A patch will follow this one to get the dependencies into the container >> images being provided by the project >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsiemens%2Fkas&data=04%7C01%7Csilvano.cirujano-cuesta%40siemens.com%7C0eb5495ba8304b61405c08d8f5eaa010%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637529735344486101%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=t9vv0Zgd6ZFbaYDdl749dyKMtLpthK4dN3kDT%2BUXsns%3D&reserved=0 (for `kas-container`, for example). >> >> Silvano Cirujano Cuesta (5): >> classes: add root filesystem containerizing class >> classes: add new image type 'container-img' >> sdk: add support for containerized sdk >> docs: document creation of container images >> ci: add container image sample configurations >> >> doc/user_manual.md | 179 ++++++++++++++++++ >> meta-isar/conf/local.conf.sample | 3 + >> meta-isar/conf/machine/container.conf | 5 + >> .../conf/multiconfig/container-bullseye.conf | 4 + >> .../conf/multiconfig/container-buster.conf | 4 + >> .../conf/multiconfig/container-stretch.conf | 4 + >> meta/classes/container-img.bbclass | 18 ++ >> .../classes/image-container-extension.bbclass | 82 ++++++++ >> meta/classes/image-sdk-extension.bbclass | 42 +++- >> meta/classes/image.bbclass | 1 + >> scripts/ci_build.sh | 29 ++- >> 11 files changed, 363 insertions(+), 8 deletions(-) >> create mode 100644 meta-isar/conf/machine/container.conf >> create mode 100644 meta-isar/conf/multiconfig/container-bullseye.conf >> create mode 100644 meta-isar/conf/multiconfig/container-buster.conf >> create mode 100644 meta-isar/conf/multiconfig/container-stretch.conf >> create mode 100644 meta/classes/container-img.bbclass >> create mode 100644 meta/classes/image-container-extension.bbclass >> > Applied to next, thanks. > Thanks for the information. I'm glad that the effort brought a result.